xfs
[Top] [All Lists]

Re: xfsdump-3.0.4 problems

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfsdump-3.0.4 problems
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 17 Aug 2010 05:03:19 -0400
Cc: Mario Bachmann <mbachman@xxxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20100817071337.GN10429@dastard>
References: <20100816182236.249a2a0f@xxxxxxxxxxx> <20100816223021.GL10429@dastard> <20100817083227.06e23889@xxxxxxxxxxx> <20100817071337.GN10429@dastard>
User-agent: Mutt/1.5.20 (2009-08-17)
On Tue, Aug 17, 2010 at 05:13:37PM +1000, Dave Chinner wrote:
> > Testing List (on one machine only):
> > works:   x86_64, 2.6.34.4, xfsdump-3.0.1
> > works:   x86_64, 2.6.34.4, xfsdump-3.0.4
> > failure: x86_64, 2.6.35.2, xfsdump-3.0.1 (worked only one time)
> > failure: x86_64, 2.6.35.2, xfsdump-3.0.4
> 
> Ok, that makes more sense - we changed the way bulkstat works in
> from 2.6.34 to 2.6.35 to correctly validate inode numbers being
> passed in via bulkstat, and hence files unlinked during the dump run
> could return EINVAL when validating the directory structure (as they
> no longer exist). Is you system completely idle while the dump
> is running, or are files being removed while the dump is running?

I've also seen related issues in xfstests recently, but even going all
the way back to kernel 2.6.34 does not solve all of them for me.

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