Messages in this thread | | | Date | Thu, 29 Jul 2004 11:30:49 +1000 | From | Nathan Scott <> | Subject | Re: XFS: how to NOT null files on fsck? |
| |
On Fri, Jul 09, 2004 at 09:37:48AM -0700, L A Walsh wrote: > It's a feature! :-) > > It's been in the code for years to randomly write nulls to some files
Pfft, nonsense. The problem relates to an updated inode size being flushed ahead of the data behind it (hence a size update can make it out before delayed allocate extents do, and we end up with a hole beyond the end of file, which reads as zeroes).
> Apparently not easily reproduced, no one has a clue why it does it. > Just does.
No, its actually well known why it behaves this way. We are looking into ways to address this, and have some ideas - the trick is fixing it without hurting write performance - which we will do, its just not trivial.
There are several techiques to reduce the impact of this behaviour, as others have described (or see the linux-xfs archives).
cheers.
-- Nathan - 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/
| |