Changes between Version 1 and Version 2 of disk_alignment
- Timestamp:
- Feb 23, 2011, 7:01:03 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
disk_alignment
v1 v2 8 8 9 9 * physical disk partitions -- should start at a multiple of 8192s (where s means "512Byte sector") 10 * RAID -- mdadm should use 0.90 or 1.0 [https://raid.wiki.kernel.org/index.php/RAID_superblock_formats superblocks], which are written at the end of the device. If metadata version 1.1 or 1.2 are used, then the `data_offset` field needs to be a multiple of 8192. 10 * RAID -- mdadm should use 0.90 or 1.0 [https://raid.wiki.kernel.org/index.php/RAID_superblock_formats superblocks], which are written at the end of the device. If metadata version 1.1 or 1.2 are used, then the `data_offset` field needs to be a multiple of 8192. [http://www.issociate.de/board/goto/2027709/Alignment_of_RAID_on_specific_boundary.html there does not seem to be a way to force a custom data_offset with metadata 1.1 or 1.2] (i filed [DebianBug:614841] as a wishlist). in squeeze, 1.2 is the default, so use `--metadata 1.0` during `mdadm --create` :( 11 11 * dm_crypt/LUKS -- `cryptsetup LuksFormat` should use `--align-payload=8192` 12 12 * LVM … … 19 19 * Partitions: (look at Start column -- you want multiples of 8192) `parted /dev/sda unit s print` 20 20 * RAID: `mdadm --examine $COMPONENTDEVICE | grep Version` 21 * if the version is 1.1 or 1.2, then look at the data offset: `mdadm --examine $COMPONENTDEVICE | grep 'Data Offset:` 21 22 * dm_crypt/LUKS: `cryptsetup luksDump $BASEDEVICE | grep '^Payload offset:'` 22 23 * LVM