xfs
[Top] [All Lists]

Re: xfsdump SGI_FS_BULKSTAT errno = 22, how could this IRIX bug get into

To: Michael Lueck <mlueck@xxxxxxxxxxxxxxxxxxxx>
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?
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 4 Feb 2011 11:08:23 +1100
Cc: Bill Kendall <wkendall@xxxxxxx>, linux-xfs@xxxxxxxxxxx, Dann Frazier <dannf@xxxxxxxxxx>
In-reply-to: <4D4ABEF7.7000400@xxxxxxxxxxxxxxxxxxxx>
References: <iibmah$dlp$1@xxxxxxxxxxxxxxx> <4D49A35B.6030009@xxxxxxx> <20110203045836.GV11040@dastard> <4D4ABEF7.7000400@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
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@xxxxxxxxxxxxx

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