[lkml]   [2004]   [Nov]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [2.6.10-rc2] XFS filesystem corruption
Nathan Scott schrieb:
> On Tue, Nov 23, 2004 at 11:13:18AM +0100, Prakash K. Cheemplavam wrote:
>>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?

No. That's why I am wondering. I read about such errors like I got
before in lkml and usually they were not fs related but libata siimage
driver related. It could be just a coincidence that it came up with xfs,
but till now (I guess 5 days now, though not 24/7 running) ext3 is
behaving nicely.


[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 14:08    [W:0.051 / U:5.788 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site