Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfsdump\:\s+use\s+the\s+full\s+32\-bit\s+generation\s+number\s*$/: 7 ]

Total 7 documents matching your query.

1. [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: Bill Kendall <wkendall@xxxxxxx>
Date: Fri, 6 Jan 2012 14:09:25 -0600
xfsdump historically has truncated the inode generation number to the low 12 bits when writing out directory entries. This makes it possible for xfsrestore to mistakingly think 2 directory entries re
/archives/xfs/2012-01/msg00073.html (32,022 bytes)

2. Re: [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: David Brown <davidb@xxxxxxxxxx>
Date: Sat, 7 Jan 2012 16:58:23 -0800
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 al
/archives/xfs/2012-01/msg00075.html (8,375 bytes)

3. Re: [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: Bill Kendall <wkendall@xxxxxxx>
Date: Mon, 09 Jan 2012 08:01:25 -0600
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 al
/archives/xfs/2012-01/msg00079.html (8,803 bytes)

4. Re: [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 5 Feb 2012 08:36:48 -0500
Shouldn't the be an option to still generate the old format for compatibility reasons?
/archives/xfs/2012-02/msg00109.html (7,347 bytes)

5. Re: [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: Bill Kendall <wkendall@xxxxxxx>
Date: Mon, 06 Feb 2012 11:40:09 -0600
Christoph Hellwig wrote: 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 m
/archives/xfs/2012-02/msg00155.html (9,090 bytes)

6. Re: [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 6 Feb 2012 12:41:40 -0500
Yes.
/archives/xfs/2012-02/msg00156.html (7,816 bytes)

7. Re: [PATCH] xfsdump: use the full 32-bit generation number (score: 1)
Author: Bill Kendall <wkendall@xxxxxxx>
Date: Tue, 07 Feb 2012 14:52:39 -0600
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?
/archives/xfs/2012-02/msg00196.html (8,958 bytes)


This search system is powered by Namazu