On Thu, Aug 02, 2001 at 07:37:50PM +0200, Matthias Andree wrote:
> So this part is covered.
>
> The other thing is, that Linux is the only known system that does
> asynchronous rename/link/unlink/symlink -- people have claimed it might
> not be the only one, but failed to name systems.
Not true. There are tons of others.
The issue was that synchronous directory updates are *optional* on
many systems (Linux included), but that Linux's support for that is
really inefficient since it ends up syncing file metadata updates too
(and it's much more efficient to use fsync for that.)
> Still, some people object to a dirsync mount option.
Who? People who have discussed this in the past have certainly not
objected to my knowledge. It would clearly help situations like this
(as would a dirsync chattr option.)
> > The prescription for symlinks is, if you want them safely on disk you
> > have to explicitly fsync the containing directory.
>
> Yes, and it doesn't matter, since MTAs don't use symlinks (symlinks
> waste inodes on most systems).
Irrelevant. We're talking about what makes sensible semantics, not
what assumptions any specific application makes. It makes no sense to
say that dirsync won't affect symlinks just because some existing
applications don't rely on that!
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/