From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>, Zhu Han <schumi.han@gmail.com>
Subject: Re: Directory fsync
Date: Sat, 24 Sep 2011 01:09:44 +0200 [thread overview]
Message-ID: <201109240109.45532@zmi.at> (raw)
In-Reply-To: <20110923163354.GA24319@infradead.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 1091 bytes --]
On Freitag, 23. September 2011 Christoph Hellwig wrote:
> As far as standards are concerned it is. As far as the current XFS
> implementation is concerned you don't need it as the file fsync will
> also force out all transactions that belong to the create.
Aren't you giving O_PONIES to the users? ;-)
I understand your description, but we should always tell people to use a
directory fsync to be sure. Their applications might run on other
filesystems, or run for 10 years, and maybe XFS's implementation changes
in between. And maybe in historical kernels even XFS's implementation
wasn't like it's now?
@schumi: If your application should be able to run in a safe way on
other filesystems, or other kernel releases, or other unixes, it's best
to fsync the directory inode too. It's better to use it always, then
nothing won't break.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-23 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 15:12 Directory fsync Zhu Han
2011-09-23 16:33 ` Christoph Hellwig
2011-09-23 23:09 ` Michael Monnerie [this message]
2011-09-24 1:20 ` Zhu Han
2011-10-01 23:20 ` Peter Grandi
2011-09-26 0:28 ` Dave Chinner
2011-09-26 0:51 ` Christoph Hellwig
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=201109240109.45532@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=hch@infradead.org \
--cc=schumi.han@gmail.com \
--cc=xfs@oss.sgi.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