From: Dave Chinner <david@fromorbit.com>
To: Ralf Gross <Ralf-Lists@ralfgross.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error xfs_da_do_buf(2)
Date: Thu, 23 Sep 2010 09:24:31 +1000 [thread overview]
Message-ID: <20100922232431.GH2614@dastard> (raw)
In-Reply-To: <20100922121123.GB23326@pirx.askja.de>
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
filesystem...
> 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.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-22 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 7:26 XFS internal error xfs_da_do_buf(2) Ralf Gross
2010-09-22 8:31 ` Emmanuel Florac
2010-09-22 19:23 ` Ralf Gross
2010-09-22 8:32 ` Dave Chinner
2010-09-22 12:11 ` Ralf Gross
2010-09-22 23:24 ` Dave Chinner [this message]
2010-09-23 8:48 ` Ralf Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100922232431.GH2614@dastard \
--to=david@fromorbit.com \
--cc=Ralf-Lists@ralfgross.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox