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
|