xfs
[Top] [All Lists]

Re: Corrupted files on 2.4.18.

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Corrupted files on 2.4.18.
From: Juri Haberland <juri@xxxxxxxxxxxxxx>
Date: Wed, 20 Mar 2002 19:32:42 +0100
Organization: totally unorganized
References: <004701c1d023$2623fcd0$3b00a8c0@aplabwp0368359> <1016638455.24127.3.camel@stout.americas.sgi.com> <1016647181.23989.153.camel@dellinux>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020305
Daniel Fonseca wrote:
> Hi Eric!
> 
> Don't you think that this is a major nuisance? I mean, I am very glad
> with XFS on the server level, but at my home machine I have ext3 and xfs
> (using, testing and comparison purposes) and everytime there's a hard
> reset (too many times lately, unfortunately) only the files on the xfs
> partition get this "screwed". Ext3 truncates (or whatever) them, but
> loosing the whole files is very bad on the user's point of view -
> configuration files, for example, drove my client applications mad to
> the point that I removed xfs completely, to avoid this. Enabling and
> pressing the Magic SysRq key and flushing out is not a clean solution,
> IMHO.
> 
> I seem to remember this being a bug reported some time ago, and thought
> it was corrected, though.

Hmm, hmm, IMO it's not a bug, but a feature ;) If you want your data
reliable on disk mount it -osync. That's what I do on partitions where I
won't risk running into this "zero"-issue. Oh well, I think we all are a
bit pampered (right word? please correct me) by ext3 :-)

> It's never enough to say how great your job has been for all of us!

Yes, indeed!

Juri


<Prev in Thread] Current Thread [Next in Thread>