summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorMikulas Patocka <mpatocka@redhat.com>2019-11-13 06:48:16 -0500
committerMike Snitzer <snitzer@redhat.com>2019-11-15 14:49:16 -0500
commitd537858ac8aaf4311b51240893add2fc62003b97 (patch)
tree7d95a35edc2d838b9a605db8bac62f39c9b1cbb5 /init
parent35ad035b8398c634d888324a299ec50a84cbc6cc (diff)
dm integrity: fix excessive alignment of metadata runs
Metadata runs are supposed to be aligned on 4k boundary (so that they work efficiently with disks with 4k sectors). However, there was a programming bug that makes them aligned on 128k boundary instead. The unused space is wasted. Fix this bug by providing a proper 4k alignment. In order to keep existing volumes working, we introduce a new flag SB_FLAG_FIXED_PADDING - when the flag is clear, we calculate the padding the old way. In order to make sure that the old version cannot mount the volume created by the new version, we increase superblock version to 4. Also in order to not break with old integritysetup, we fix alignment only if the parameter "fix_padding" is present when formatting the device. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions