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: Fri, 4 Feb 2011 11:08:23 +1100 [thread overview]
Message-ID: <20110204000823.GW11040@dastard> (raw)
In-Reply-To: <4D4ABEF7.7000400@lueckdatasystems.com>
On Thu, Feb 03, 2011 at 09:43:03AM -0500, Michael Lueck wrote:
> Dave Chinner wrote:
> >So bulkstat got EINVAL returned for and inode that it was looking
> >up. That implies that it was racing with an unlink, which is
> >what the above commits catch and prevent. Can you run xfsdump with
> >full debug output (-v 5) so we can see what inode is being operated
> >on when this failure occurs?
>
> Thank you so much Dave!
>
> Please find the trace output here in zipped format:
>
> http://www.lueckdatasystems.com/pub/ldsbackup.trace.log.zip
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. The inode it is
starting at when it returns EINVAL is 80508397. Can you firstly
post the output of:
# xfs_db -c "inode 80508397" -c p <dev>
And can you also run 'xfs_repair -n <dev>' on the filesystem and
post the output as well so we can see what state the filesytem is
in?
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 0:05 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 [this message]
2011-02-04 14:12 ` Michael Lueck
2011-02-04 20:49 ` Dave Chinner
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=20110204000823.GW11040@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