From: Al Boldi Subject: Re: konqueror deadlocks on 2.6.22 Date: Tue, 22 Jan 2008 21:54:25 +0300 Message-ID: <200801222154.25828.a1426z@gawab.com> References: <200801192114.41427.a1426z@gawab.com> <200801221623.42989.a1426z@gawab.com> <200801220925.50314.chris.mason@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Ingo Molnar , Oliver Pinter (=?iso-8859-1?q?Pint=E9r?= =?iso-8859-1?q?=20Oliv=E9r?=) , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Chris Mason Return-path: Received: from [212.12.190.184] ([212.12.190.184]:54048 "EHLO raad.intranet" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752389AbYAVTKa (ORCPT ); Tue, 22 Jan 2008 14:10:30 -0500 In-Reply-To: <200801220925.50314.chris.mason@oracle.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Chris Mason wrote: > Running fsync in data=ordered means that all of the dirty blocks on the FS > will get written before fsync returns. Hm, that's strange, I expected this kind of behaviour from data=journal. data=writeback should return immediatly, which seems it does, but data=ordered should only wait for metadata flush, it shouldn't wait for filedata flush. Are you sure it waits for both? Thanks! -- Al