xfs
[Top] [All Lists]

Re: Corrupted log after crash

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Corrupted log after crash
From: Michael Loftis <mloftis@xxxxxxxxx>
Date: Sun, 30 Jan 2005 14:51:16 -0700
In-reply-to: <2bf8aba0501301142169146eb@mail.gmail.com>
References: <2bf8aba0501301142169146eb@mail.gmail.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Sounds to me like someone is lying (some of your hardware that is)...Either the IDE drives are lying, the highpoitn ctonroller/rocketraid is lying or possibly the kernel driver. What is the lie? The lie is about when a disk write is actually committed to disk. XFS, JFS, and EXT3 all count on the hardware actually having the log safely on disk when they say it is. Lots of lower end RAID hardware lies about this.

Easiest way is to try completely turning off write caching if the controller allows it. Linux already does a pretty good job of write caching, so you may (probably won't) notice performance changes.

Could still be a bug in XFS, but it really does kind of seem like a lying piece of hardware.


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