[Top] [All Lists]

Re: XFS internal error xfs_da_do_buf(2)

To: Ralf Gross <Ralf-Lists@xxxxxxxxxxxx>
Subject: Re: XFS internal error xfs_da_do_buf(2)
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 23 Sep 2010 09:24:31 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20100922121123.GB23326@xxxxxxxxxxxxx>
References: <20100922083226.GF2614@dastard> <20100922121123.GB23326@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Wed, Sep 22, 2010 at 02:11:23PM +0200, Ralf Gross wrote:
> Dave Chinner schrieb:
> > On Wed, Sep 22, 2010 at 09:26:53AM +0200, Ralf Gross wrote:
> > > Any hints what to look for or what to do to notice this corruption as 
> > > soon as possible?
> > 
> > You won't find an error on disk without scrubbing of some kind.
> > In the case of filesystem metadata, you need to read all the
> > metadata and validity check it to find random corruptions. The best
> > you can do is traverse and stat every file regularly...
> Disk scrubbing is activated on the infortrend RAIDs (2 week schedule).

Ok, so that should catch bit errors as a result of disk write/read
errors, but it would take 2 weeks to find it. That still leaves a
window for undetected disk corruption to be trippd over by the

> With 'stat every file regularly' you mean check the md5sum?

If you just want to read the metadata, then just doing something
like a 'ls -R <mntpt>' will read every directory block and inode and
run the checks that trigger the errors you are seeing. running
md5sum on every file will check the data as well, but will take a
lot longer.


Dave Chinner

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