xfs
[Top] [All Lists]

Re: Corrupted files on 2.4.18.

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Corrupted files on 2.4.18.
From: Daniel Fonseca <daniel@xxxxxxxxxxxx>
Date: 20 Mar 2002 17:59:41 +0000
In-reply-to: <1016638455.24127.3.camel@xxxxxxxxxxxxxxxxxxxxxx>
References: <004701c1d023$2623fcd0$3b00a8c0@aplabwp0368359> <1016638455.24127.3.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
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.

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

Cheers,
Daniel

On Wed, 2002-03-20 at 15:34, Eric Sandeen wrote:
> The real culprit here is the fact that your machine locked up - when
> this happens, there's no telling what data may or may not get down to
> the disk.
> 
> The ^@ (null) characters you saw as a result are explained in the FAQ.
> 



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