Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932510AbWCNVvZ (ORCPT ); Tue, 14 Mar 2006 16:51:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751929AbWCNVvY (ORCPT ); Tue, 14 Mar 2006 16:51:24 -0500 Received: from duke.cs.duke.edu ([152.3.140.1]:65527 "EHLO duke.cs.duke.edu") by vger.kernel.org with ESMTP id S1751944AbWCNVvY (ORCPT ); Tue, 14 Mar 2006 16:51:24 -0500 Date: Tue, 14 Mar 2006 16:51:13 -0500 (EST) From: Tong Li To: "Theodore Ts'o" cc: linux-kernel@vger.kernel.org Subject: Re: Bursty I/O in ext3 In-Reply-To: <20060314152952.GA5644@thunk.org> Message-ID: References: <20060314152952.GA5644@thunk.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 583 Lines: 18 > If you are using an e2fsprogs older than version 1.38, you should try > expanding the journal size from the default of 32M to 128M; with the > filesystem unmounted do: > > tune2fs -O ^has_journal /dev/hdXX > tune2fs -O has_journal -J journal_size=128 /dev/hdXX > I did this and yes, it fixed the problem. Thank you so much, tong - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/