On Sun, Aug 05, 2007 at 09:57:02AM +0200, Florian Weimer wrote: > For instance, some editors don't perform fsync-then-rename, but simply > truncate the file when saving (because they want to preserve hard > links). With XFS, this tends to cause null bytes on crashes. Since > ext3 has got a much larger install base, this would result in lots of > bug reports, I fear. XFS has recently been changed to only updated the on-disk i_size after data writeback has finished to get rid of this irritation. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 00/23] per device dirty throttling -v8
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Andrew Morton <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Florian Weimer <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Andrew Morton <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
- From: Florian Weimer <[email protected]>
- [PATCH 00/23] per device dirty throttling -v8
- Prev by Date: Re: [patch] implement smarter atime updates support, v2
- Next by Date: Re: [1/3] 2.6.23-rc2: known regressions
- Previous by thread: Re: [PATCH 00/23] per device dirty throttling -v8
- Next by thread: Re: [PATCH 00/23] per device dirty throttling -v8
- Index(es):