Lines Matching +full:super +full:- +full:set

2 dm-zoned
5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
7 pattern constraints. In effect, it implements a drive-managed zoned
10 host-managed zoned block devices and can mitigate the potential
11 device-side performance degradation due to excessive random writes on
12 host-aware zoned block devices.
21 http://www.t13.org/Documents/UploadedDocuments/docs2015/di537r05-Zoned_Device_ATA_Command_Set_ZAC.p…
23 The dm-zoned implementation is simple and minimizes system overhead (CPU
25 host-managed disk with 256 MB zones, dm-zoned memory usage per disk
29 dm-zoned target devices are formatted and checked using the dmzadm
32 https://github.com/hgst/dm-zoned-tools
37 dm-zoned implements an on-disk buffering scheme to handle non-sequential
58 dm-zoned exposes a logical device with a sector size of 4096 bytes,
63 The on-disk metadata format is as follows:
66 super block which describes the on disk amount and position of metadata
69 2) Following the super block, a set of blocks is used to describe the
77 3) A set of blocks used to store bitmaps indicating the validity of
118 system crash, 2 sets of metadata zones are used. One set, the primary
119 set, is used as the main metadata region, while the secondary set is
121 secondary set and validated by updating the super block in the secondary
122 set, a generation counter is used to indicate that this set contains the
124 block updates can be done in the primary metadata set. This ensures that
125 one of the set is always consistent (all modifications committed or none
135 a third set of metadata (without the zone bitmaps) is written to the
150 	dmzadm --format /dev/sdxx
158 	dmzadm --format /dev/sdxx /dev/sdyy
165 	dmzadm --start /dev/sdxx /dev/sdyy
173 	dmsetup status /dev/dm-X
191 	dmsetup message /dev/dm-X 0 reclaim