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

xfs

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:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:	Sun, 5 Feb 2012 08:36:48 -0500
Cc:	xfs@xxxxxxxxxxx
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:
> 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.

Shouldn't the be an option to still generate the old format for
compatibility reasons?

[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: sparsify - utility to punch out blocks of 0s in a file, Ron Yorston
Next by Date:	Re: sparsify - utility to punch out blocks of 0s in a file, Raghavendra D Prabhu
Previous by Thread:	Re: [PATCH 2/8] vfs: Protect write paths by sb_start_write - sb_end_write, Eric Sandeen
Next by Thread:	Re: [PATCH] xfsdump: use the full 32-bit generation number, Bill Kendall
Indexes:	[Date] [Thread] [Top] [All Lists]