linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Al Boldi <a1426z@gawab.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Oliver Pinter" <oliver.pntr@gmail.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: konqueror deadlocks on 2.6.22
Date: Tue, 22 Jan 2008 14:13:57 -0500	[thread overview]
Message-ID: <200801221413.58337.chris.mason@oracle.com> (raw)
In-Reply-To: <200801222154.25828.a1426z@gawab.com>

On Tuesday 22 January 2008, Al Boldi wrote:
> 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?

I over simplified.  data=ordered means that all data blocks are written before 
the metadata that references them commits.

So, if you add 1GB to a fileA in a transaction and then run fsync(fileB) in 
the same transaction, the 1GB from fileA is sent to disk (and waited on) 
before the fsync on fileB returns.

-chris

  reply	other threads:[~2008-01-22 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 18:14 konqueror deadlocks on 2.6.22 Al Boldi
2008-01-19 18:53 ` Oliver Pinter (Pintér Olivér)
2008-01-19 20:57   ` Al Boldi
2008-01-19 22:17     ` Oliver Pinter (Pintér Olivér)
2008-01-22 10:10       ` Ingo Molnar
2008-01-22 13:23         ` Al Boldi
2008-01-22 14:25           ` Chris Mason
2008-01-22 18:54             ` Al Boldi
2008-01-22 19:13               ` Chris Mason [this message]
     [not found] ` <1200802290.4166.2.camel@homer.simson.net>
2008-01-20  5:41   ` Al Boldi
2008-01-20  7:23     ` Mike Galbraith
2008-01-20  7:30     ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801221413.58337.chris.mason@oracle.com \
    --to=chris.mason@oracle.com \
    --cc=a1426z@gawab.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oliver.pntr@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).