Search String: Display: Description: Sort:

Results:

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

Total 4 documents matching your query.

1. [PATCH v2] xfsdump: use the full 32-bit generation number (score: 1)
Author: Bill Kendall <wkendall@xxxxxxx>
Date: Thu, 9 Feb 2012 12:46:20 -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-02/msg00230.html (50,688 bytes)

2. Re: [PATCH v2] xfsdump: use the full 32-bit generation number (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 12 Feb 2012 18:47:20 -0500
Looks generally good to me, but is there any good reason to not make the -K argument extensible by requiring a version argument, even if that one currently only supports 2 and 3 as valid values?
/archives/xfs/2012-02/msg00269.html (7,515 bytes)

3. Re: [PATCH v2] xfsdump: use the full 32-bit generation number (score: 1)
Author: Bill Kendall <wkendall@xxxxxxx>
Date: Mon, 13 Feb 2012 10:36:24 -0600
I thought about doing that, but given the low frequency of format changes decided it could wait until there's more than one old format to support. -K without an argument could be treated as "generate
/archives/xfs/2012-02/msg00276.html (9,028 bytes)

4. Re: [PATCH v2] xfsdump: use the full 32-bit generation number (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 13 Feb 2012 11:45:20 -0500
Ok, sounds fine. I'll put it into the repository and after that we should aim for an xfsdump 3.1.0 release ASAP.
/archives/xfs/2012-02/msg00277.html (9,333 bytes)


This search system is powered by Namazu