public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Kendall <wkendall@sgi.com>
To: David Brown <davidb@davidb.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: use the full 32-bit generation number
Date: Mon, 09 Jan 2012 08:01:25 -0600	[thread overview]
Message-ID: <4F0AF335.5070905@sgi.com> (raw)
In-Reply-To: <20120108005822.GA32313@davidb.org>

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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-01-09 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 20:09 [PATCH] xfsdump: use the full 32-bit generation number Bill Kendall
2012-01-08  0:58 ` David Brown
2012-01-09 14:01   ` Bill Kendall [this message]
2012-02-05 13:36 ` Christoph Hellwig
2012-02-06 17:40   ` Bill Kendall
2012-02-06 17:41     ` Christoph Hellwig
2012-02-07 20:52       ` Bill Kendall

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=4F0AF335.5070905@sgi.com \
    --to=wkendall@sgi.com \
    --cc=davidb@davidb.org \
    --cc=xfs@oss.sgi.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