Messages in this thread | | | Date | Fri, 9 Jul 2004 14:59:55 -0700 | From | Chris Wedgwood <> | Subject | Re: XFS: how to NOT null files on fsck? |
| |
On Fri, Jul 09, 2004 at 09:37:48AM -0700, L A Walsh wrote:
> Even after multiple syncs, files edited within the past few days > will sometimes go mysteriously null. Good reason to do daily > backups as the backups will usually contain the correct file...
I *never* see this even when beating the hell out of machines and trying to break things.
I do see nulls in cases where the metadata was updated and the data didn't flush, that's supposed to happen.
> Now if we could just come up with a reproducable test case...but > when I try to reproduce it, it doesn't. Grrr....it knows when I'm > scrutinizing!! :-)
Use anything that handles dotfiles or configuration badly (ie. KDE), make some changes or just 'run it' for a bit. Every now something rewrites some files. Yank the power a few times and sooner or later you'll end up with problems under KDE certainly.
Sane applications (MTAs like postfix for example) don't have this problem because they were written with more clue. If they did have this problem people would scream, because mail would get lost... and large mail servers might have tens of thousands of files moving about in-flight, much more strenuous that a few dot-files.
--cw - 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/
| |