xfs
[Top] [All Lists]

Re: Xfs Access to block zero exception and system crash

To: Sagar Borikar <sagar_borikar@xxxxxxxxxxxxxx>
Subject: Re: Xfs Access to block zero exception and system crash
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 04 Jul 2008 10:33:20 -0500
Cc: Nathan Scott <nscott@xxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <486DF8F0.5010700@xxxxxxxxxxxxxx>
References: <20080628000516.GD29319@disturbed> <340C71CD25A7EB49BFA81AE8C8392667028A1CA7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080629215647.GJ29319@disturbed> <20080630034112.055CF18904C4@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4868B46C.9000200@xxxxxxxxxxxxxx> <20080701064437.GR29319@disturbed> <486B01A6.4030104@xxxxxxxxxxxxxx> <20080702051337.GX29319@disturbed> <486B13AD.2010500@xxxxxxxxxxxxxx> <1214979191.6025.22.camel@xxxxxxxxxxxxxxxxxx> <20080702065652.GS14251@xxxxxxxxxxxxxxxxxxxxx> <486B6062.6040201@xxxxxxxxxxxxxx> <486C4F89.9030009@xxxxxxxxxxx> <486C6053.7010503@xxxxxxxxxxxxxx> <486CE9EA.90502@xxxxxxxxxxx> <486DF8F0.5010700@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
Sagar Borikar wrote:

>>   
> Even we too don't want to leave it as it is.  I still am working on back 
> porting the latest xfs code.
> Your patches are helping a lot .
> Just to check whether that issue lies with 2.6.18 or MIPS port, I tested 
> it on 2.6.24 x86 platform.
> Here we created a loop back device of 10 GB and mounted xfs on that.
> What I observe that xfs_repair reports quite a few bad blocks and bad 
> extents here as well.
> So is developing bad blocks and extents  normal behavior in xfs which 
> would be recovered
> in background or is it a bug? I still didn't see the exception but the 
> bad blocks and extents are
> generated within 10 minutes or running the tests.
> Attaching the log .

Repair finding corruption indicates a bug (or hardware problem) somewhere.

As a long shot you might re-test with this patch in place:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=6ab455eeaff6893cd06da33843e840d888cdc04a

But, as Dave said, please also provide the testcase.

-Eric


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