From: Bill Kendall <wkendall@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: use the full 32-bit generation number
Date: Tue, 07 Feb 2012 14:52:39 -0600 [thread overview]
Message-ID: <4F318F17.4010504@sgi.com> (raw)
In-Reply-To: <20120206174140.GA10315@infradead.org>
Christoph Hellwig wrote:
> On Mon, Feb 06, 2012 at 11:40:09AM -0600, Bill Kendall wrote:
>> You were referring to an xfsdump option. What use case did you
>> have in mind? Compatibility with an old restore?
>
> Yes.
Ok, I can see the value in that if a filesystem is being moved
to another system which has an older xfsrestore.
I'll repost with that change as well as with an option for
xfsrestore to truncate all generation numbers down to 12-bits
as mentioned in my last mail.
Bill
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-02-07 20:52 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
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 [this message]
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=4F318F17.4010504@sgi.com \
--to=wkendall@sgi.com \
--cc=hch@infradead.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