xfs
[Top] [All Lists]

Re: [PATCH] xfsdump: use the full 32-bit generation number

To: David Brown <davidb@xxxxxxxxxx>
Subject: Re: [PATCH] xfsdump: use the full 32-bit generation number
From: Bill Kendall <wkendall@xxxxxxx>
Date: Mon, 09 Jan 2012 08:01:25 -0600
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20120108005822.GA32313@xxxxxxxxxx>
References: <1325880565-20934-1-git-send-email-wkendall@xxxxxxx> <20120108005822.GA32313@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16
On 01/07/2012 06:58 PM, David Brown wrote:
On Fri, Jan 06, 2012 at 02:09:25PM -0600, Bill Kendall wrote:

This patch changes xfsdump to use the full 32-bit inode generation
number.
A change to part of the dump format (direnthdr_t) was required, so the
dump format version has been bumped to 3. xfsdump also required
changes to
its inode-to-generation cache. This map is not persistent though, so no
compatibility or version changes were required there.

I suspect that this does fix the problem. Since the fix is in the
dump, not just restore, I guess I'll just have to start with a fresh
level 0 and see if the failure ever happens again upon restore.

That's right. If you need to recover files from the backup that has
issues, try applying only your level 1 backup and select just the
files that failed to restore.

Bill

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