mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Xin Zhao" <uszhaoxin@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: How to know when file data has been flushed into disk?
Date: Fri, 7 Apr 2006 12:04:51 -0400	[thread overview]
Message-ID: <4ae3c140604070904j51d1b968l2f62a1de647c0b02@mail.gmail.com> (raw)
In-Reply-To: <87slop1ix2.fsf@suzuka.mcnaught.org>

Thanks for your reply.

That make sense. But at least ext3 needs to know when all data has
been flushed so that it can commit the meta data. Question is how can
ext3 knows that? The data flushing is done by flush daemon. There go
to be some way to notify ext3 that data is flushed. Where  is this
part of code in ext3 module?

Xin

On 4/7/06, Douglas McNaught <doug@mcnaught.org> wrote:
> "Xin Zhao" <uszhaoxin@gmail.com> writes:
>
> > 3. Does sys_close() have to  be blocked until all data and metadata
> > are committed? If not, sys_close() may give application an illusion
> > that the file is successfully written, which can cause the application
> > to take subsequent operation. However, data flush could be failed. In
> > this case, file system seems to mislead the application. Is this true?
> > If so, any solutions?
>
> The fsync() call is the way to make sure written data has hit the
> disk.  close() doesn't guarantee that.
>
> -Doug
>

  reply	other threads:[~2006-04-07 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 15:42 Xin Zhao
2006-04-07 15:53 ` Douglas McNaught
2006-04-07 16:04   ` Xin Zhao [this message]
2006-04-07 16:55     ` linux-os (Dick Johnson)
2006-04-07 17:19       ` Xin Zhao
2006-04-07 23:54   ` Ric Wheeler
2006-04-07 17:54 ` Zach Brown
2006-04-08  1:39   ` Xin Zhao
2006-04-07 21:07 Michael Guo

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=4ae3c140604070904j51d1b968l2f62a1de647c0b02@mail.gmail.com \
    --to=uszhaoxin@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®