[Top] [All Lists]

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

To: Bill Kendall <wkendall@xxxxxxx>
Subject: Re: [PATCH] xfsdump: use the full 32-bit generation number
From: David Brown <davidb@xxxxxxxxxx>
Date: Sat, 7 Jan 2012 16:58:23 -0800
Cc: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=/doVd7HDlGjBvIBWS9/uWgca7eM=; b=ZyC7aAWhoySywYhcZB+eHYCYvSP4 1DEYyZynpZEcxpBPatNtO3XTd02iiLszU6PTNGnXOr7jmqSdTAZ8CTSJI3eipksX j5Yfk1F3IbVji0sbhh2Vjq0Sa7/1RpFx+2jGwBbPYFLB+8buR14WeUYrGUl9vjzS d3hoPIUwCUR5p0Y=
In-reply-to: <1325880565-20934-1-git-send-email-wkendall@xxxxxxx>
References: <1325880565-20934-1-git-send-email-wkendall@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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.


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