Re: XFS corruption during power-blackout

[Christian Rice <xian@tippett.com>]

Al Boldi wrote:

> Hi Nathan,
> You wrote: {
> On Tue, Jun 28, 2005 at 12:08:05PM +0300, Al Boldi wrote:
>  
>
> > True now, not so around 2.4.20 when XFS was rock-solid. I think they 
> > tried to improve on performance and broke something. I wish they would 
> > fix that because it forced me back to ext3, as in consistency over 
> > performance any time.
> >    
>
> Can you provide any details...
> }
>
> Specifically, in 2.4.20 I did an acid test:
> Spawn 10 cp -a on some big dir like /usr.
> Let it run for a few seconds, then pull the plug.
> Don't reset-button, reset is different then pulling the plug.
> Don't poweroff-button, poweroff is different then pulling the plug.
> On reboot diff the dirs spawned.
>
> What I found were 4 things in the dest dir:
> 1. Missing Dirs,Files. That's OK.
> 2. Files of size 0. That's acceptable.
> 3. Corrupted Files. That's unacceptable.
> 4. Corrupted Files with original fingerprint. That's ABSOLUTELY
> unacceptable.
>
> Ext3 performed best with minimal files of size 0.
> XFS was second  with more files of size 0.
> Reiser,JFS was worst with corruptions.
>
> When XFS was added into the vanilla-Kernel it caused corruptions like Reiser
> and JFS, which forced me back to Ext3.
>
>
>
>  
Pardon me if I haven't seen the whole thread.

Do you have hard drive write cache turned off or, if it's a raid card, a 
battery backup on the write cache?  That makes a big difference when 
operators begin doing things like pulling plugs and hitting reset.

Again, no offense, just one of those "have you taken it out of the box, 
plugged it in and turned it on" kind of questions.
-
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/