From: Vijayan Prabhakaran <pvijayan@gmail.com>
To: Perry Kundert <perry.kundert@gmail.com>, reiserfs-list@namesys.com
Subject: Re: BUG in writeback mode - from data journaling patch
Date: Mon, 30 Aug 2004 12:12:43 -0500 [thread overview]
Message-ID: <d68fdf7d04083010125e1f2de3@mail.gmail.com> (raw)
In-Reply-To: <2f9ccaae04083010074d49a0a0@mail.gmail.com>
No. That is wrong. If the syntax of the call is to update a stat
block, it must be done before the call finishes.
On Mon, 30 Aug 2004 11:07:57 -0600, Perry Kundert
<perry.kundert@gmail.com> wrote:
> On Mon, 30 Aug 2004 11:50:46 -0500, Vijayan Prabhakaran
> <pvijayan@gmail.com> wrote:
> > The fsync man page reads as:
> >
> > "...fsync copies all in-core parts of a file to disk, and waits until
> > the device reports that all parts are on stable storage. It also
> > updates metadata stat information."
> >
> > So, according to POSIX standards, the stat data must be updated on fsyncs.
> >
> Looks like it is not absolutely clear on *when* the stat metadata
> needs to be updated, though. Perhaps if it is updated later than the
> "...parts are on stable storage" that is must wait for...
>
next prev parent reply other threads:[~2004-08-30 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 18:32 BUG in writeback mode - from data journaling patch Vijayan Prabhakaran
2004-08-30 16:03 ` Dieter Nützel
2004-08-30 16:32 ` Konstantin Besch
2004-08-30 16:42 ` Chris Mason
2004-08-30 16:50 ` Vijayan Prabhakaran
[not found] ` <2f9ccaae04083010074d49a0a0@mail.gmail.com>
2004-08-30 17:12 ` Vijayan Prabhakaran [this message]
2004-08-30 17:09 ` Vijayan Prabhakaran
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=d68fdf7d04083010125e1f2de3@mail.gmail.com \
--to=pvijayan@gmail.com \
--cc=perry.kundert@gmail.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.