Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*REVIEW\:\s+Zero\s+rest\s+of\s+superblock\s+sector\s+always\s*$/: 12 ]

Total 12 documents matching your query.

1. REVIEW: Zero rest of superblock sector always (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxx>
Date: Wed, 03 Sep 2008 16:51:19 +1000
I found that zeroing the "garbage" beyond the end of the superblock in the first sector of each AG rather inconsistant. It depended on some obscure combination of version bits to be set. The followin
/archives/xfs/2008-09/msg00022.html (20,741 bytes)

2. Re: REVIEW: Zero rest of superblock sector always (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxx>
Date: Wed, 03 Sep 2008 16:52:09 +1000
BTW. If it wasn't obvious, it's for xfs_repair :) On Wed, 03 Sep 2008 16:51:19 +1000, Barry Naujok <bnaujok@xxxxxxx> wrote: I found that zeroing the "garbage" beyond the end of the superblock in the
/archives/xfs/2008-09/msg00023.html (21,612 bytes)

3. Re: REVIEW: Zero rest of superblock sector always (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 3 Sep 2008 08:18:44 -0400
Looks good. And we'll always need the rest of the sector zeroed once the superblock grows a crc field.
/archives/xfs/2008-09/msg00028.html (8,187 bytes)

4. Re: REVIEW: Zero rest of superblock sector always (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 4 Sep 2008 09:12:20 +1000
Just for filling out hte history, that isfixing a bug in an old, old mkfs.xfs on Irix where a certain version failed to zero the superblock(s) before initialising them. Every XFS filesystem made in t
/archives/xfs/2008-09/msg00033.html (8,618 bytes)

5. TCH V2] Don't do I/O beyond eof when unreserving space (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxx>
Date: Wed, 03 Sep 2008 16:51:19 +1000
nrefer
/archives/xfs/2008-09/msg00530.html (20,557 bytes)

6. ng space (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxx>
Date: Wed, 03 Sep 2008 16:52:09 +1000
llowin
/archives/xfs/2008-09/msg00531.html (21,428 bytes)

7. k tracing allocation sizes (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 3 Sep 2008 08:18:44 -0400
good.
/archives/xfs/2008-09/msg00536.html (8,007 bytes)

8. lock inodes in ALL secondaries (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 4 Sep 2008 09:12:20 +1000
943,040
/archives/xfs/2008-09/msg00541.html (8,438 bytes)

9. REVIEW: Zero rest of superblock sector always (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxx>
Date: Wed, 03 Sep 2008 16:51:19 +1000
I found that zeroing the "garbage" beyond the end of the superblock in the first sector of each AG rather inconsistant. It depended on some obscure combination of version bits to be set. The followin
/archives/xfs/2008-09/msg01038.html (20,056 bytes)

10. Re: REVIEW: Zero rest of superblock sector always (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxx>
Date: Wed, 03 Sep 2008 16:52:09 +1000
BTW. If it wasn't obvious, it's for xfs_repair :) I found that zeroing the "garbage" beyond the end of the superblock in the first sector of each AG rather inconsistant. It depended on some obscure c
/archives/xfs/2008-09/msg01039.html (20,937 bytes)

11. Re: REVIEW: Zero rest of superblock sector always (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 3 Sep 2008 08:18:44 -0400
Looks good. And we'll always need the rest of the sector zeroed once the superblock grows a crc field.
/archives/xfs/2008-09/msg01044.html (8,057 bytes)

12. Re: REVIEW: Zero rest of superblock sector always (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 4 Sep 2008 09:12:20 +1000
Just for filling out hte history, that isfixing a bug in an old, old mkfs.xfs on Irix where a certain version failed to zero the superblock(s) before initialising them. Every XFS filesystem made in t
/archives/xfs/2008-09/msg01049.html (8,488 bytes)

Current List: 1 - 12
Page: [1]
This search system is powered by Namazu