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:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
