xfs
[Top] [All Lists]

Re: [2.6.10-rc2] XFS filesystem corruption

To: "Prakash K. Cheemplavam" <prakashkc@xxxxxx>
Subject: Re: [2.6.10-rc2] XFS filesystem corruption
From: Nathan Scott <nathans@xxxxxxx>
Date: Wed, 24 Nov 2004 08:27:36 +1100
Cc: William Lee Irwin III <wli@xxxxxxxxxxxxxx>, Jan De Luyck <lkml@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <41A30D3E.9090506@xxxxxx>; from prakashkc@xxxxxx on Tue, Nov 23, 2004 at 11:13:18AM +0100
References: <200411221530.30325.lkml@xxxxxxxxx> <20041122155106.GG2714@xxxxxxxxxxxxxx> <41A30D3E.9090506@xxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Tue, Nov 23, 2004 at 11:13:18AM +0100, Prakash K. Cheemplavam wrote:
> 
> While we are at it: Is xfs known to be broken while preempt is on? (Esp 

Nope.

> using ck's preemp big kernel lock?) I got following using a raid0 setup 
> with xfs. I thought it would be a driver issue, but reformatting to ext3 
> the stripe array runs now w/o probs for a few days. (xfs crapped out 
> after a few hours on heavy disk activity.)
> ...
> Nov 21 10:10:45 tachyon end_request: I/O error, dev sdb, sector 10480855
> Nov 21 10:10:45 tachyon I/O error in filesystem ("md0") meta-data dev 
> md0 block 0x13fd990       ("xfs_trans_read_buf") error 5 buf count 8192

This looks like your driver passed an error back up to the
filesystem while it was doing metadata IO and XFS chose to
shut it down to prevent further damage.  It's unlikely to
be a preempt/xfs problem.  Possibly hardware.  Did you see
any of those device errors since switching to ext3?

cheers.

-- 
Nathan


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