From: Dave Chinner <david@fromorbit.com>
To: Michael Lueck <mlueck@lueckdatasystems.com>
Cc: linux-xfs@oss.sgi.com, Dann Frazier <dannf@debian.org>
Subject: Re: xfsdump SGI_FS_BULKSTAT errno = 22, how could this IRIX bug get into Ubuntu 10.04 Lucid between kernels 2.6.32-27 and 2.6.32-26?
Date: Sat, 5 Feb 2011 07:49:27 +1100 [thread overview]
Message-ID: <20110204204927.GZ11040@dastard> (raw)
In-Reply-To: <4D4C0965.9010905@lueckdatasystems.com>
On Fri, Feb 04, 2011 at 09:12:53AM -0500, Michael Lueck wrote:
> Dave Chinner wrote:
> >Ok, so xfsdump i seeing a short bulkstat, then an EINVAL returned
> >from the next bulkstat. That's not a race condition, and makes me
> >think you have some kind of on-disk corruption.
>
> Very odd that some kind of on-disk corruption is suddenly causing
> xfsdump problems starting with Ubuntu 10.04 (Lucid) kernel
> 2.6.32-27 and persisting in 2.6.32-28.
Not really. The newer kernels have code in them that does more
validity checks than previous kernels, so older kernels would have
erroneously and silently returned unlinked files to xfsdump and have
them backed up. IOWs, you'd never notice such a corruption with
xfsdump. On the new kernel, xfsdump gets an EINVAL error to such
occurrences, which it should have in the first place.
> And there is one other person who confirmed this xfsdump problem
> running Lucid with kernel 2.6.32-28. They reported their "me too"
> in the Ubuntu bug tracker.
>
> Could it be that 2.6.32-26 and prior managed to write something to
> disk corrupted, and the newer code is tripping on it?
That's what I'm trying to find out. Or it could be something as
simple as your disk has had an undetected bit error that has flipped
a bit in the inode allocation btree.
> I shall reboot the server to the 2.6.32-28 kernel and perform the
> tests you requested.
No need to change kernels to run xfs_repair....
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:[~2011-02-04 20:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 13:30 xfsdump SGI_FS_BULKSTAT errno = 22, how could this IRIX bug get into Ubuntu 10.04 Lucid between kernels 2.6.32-27 and 2.6.32-26? Michael Lueck
2011-02-02 18:32 ` Bill Kendall
2011-02-02 19:03 ` Michael Lueck
2011-02-03 4:58 ` Dave Chinner
2011-02-03 14:43 ` Michael Lueck
2011-02-04 0:08 ` Dave Chinner
2011-02-04 14:12 ` Michael Lueck
2011-02-04 20:49 ` Dave Chinner [this message]
2011-02-07 20:55 ` Bill Kendall
2011-02-07 21:23 ` Dave Chinner
2011-02-07 21:42 ` Bill Kendall
2011-02-07 22:04 ` Dave Chinner
2011-02-09 1:24 ` Bill Kendall
2011-02-08 17:39 ` Michael Lueck
2011-02-08 19:52 ` Dave Chinner
2011-02-08 19:59 ` Michael Lueck
2011-02-08 20:24 ` Michael Lueck
2011-02-08 22:47 ` Dave Chinner
2011-02-14 2:52 ` Michael Lueck
2011-02-08 17:39 ` Michael Lueck
2011-02-03 14:51 ` Michael Lueck
2011-02-04 14:52 ` dann frazier
2011-04-22 12:34 ` Michael Lueck
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=20110204204927.GZ11040@dastard \
--to=david@fromorbit.com \
--cc=dannf@debian.org \
--cc=linux-xfs@oss.sgi.com \
--cc=mlueck@lueckdatasystems.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