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

xfs

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

To:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject:	Re: [PATCH] xfsdump: use the full 32-bit generation number
From:	Bill Kendall <wkendall@xxxxxxx>
Date:	Tue, 07 Feb 2012 14:52:39 -0600
Cc:	xfs@xxxxxxxxxxx
In-reply-to:	<20120206174140.GA10315@xxxxxxxxxxxxx>
References:	<1325880565-20934-1-git-send-email-wkendall@xxxxxxx> <20120205133648.GA27225@xxxxxxxxxxxxx> <4F301079.9010505@xxxxxxx> <20120206174140.GA10315@xxxxxxxxxxxxx>
User-agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [PATCH] xfsdump: use the full 32-bit generation number, Christoph Hellwig Re: [PATCH] xfsdump: use the full 32-bit generation number, Bill Kendall Re: [PATCH] xfsdump: use the full 32-bit generation number, Christoph Hellwig Re: [PATCH] xfsdump: use the full 32-bit generation number, Bill Kendall <=

Previous by Date:	Re: [PATCH 3/3] filemap: don't call generic_write_sync for -EIOCBQUEUED, Jeff Moyer
Next by Date:	Re: [PATCH 3/8] xfsprogs: xfs_repair: don't set the root inode pointer, Kevan Rehm
Previous by Thread:	Re: [PATCH] xfsdump: use the full 32-bit generation number, Christoph Hellwig
Next by Thread:	[PATCH][RFC] XFS: Fix mem leak and possible NULL deref in xfs_setattr_nonsize(), Jesper Juhl
Indexes:	[Date] [Thread] [Top] [All Lists]