Eric Sandeen wrote:
So, we switch to xfs as the default FS? :-)
XFS has a nasty bug where it will leave files full of zeros on disk in a
crash.
No, it doesn't. Not any more (and technically not ever; what happened
was a truncate & extension of the file (like vi might do) led to a size
on disk but no extents so you got a sparse file. If the apps looked
after their data as they should, this wouldn't happen either, but that's
just an aside).
But anyway,
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=ba87ea699ebd9dd577bf055ebc4a98200e337542
I think it was Alan Cox that said this could be fixed quite easily by
changing the write ordering for XFS, but that someone who was willing to
maintain the patch would need to do it.
If this was merged I would love to move to XFS :)
Hasn't there always been a problem with xfs and 4k stacks? Or are you
only talking about 64-bit versions here?
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
