summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorXiao Ni <xni@redhat.com>2017-07-05 17:34:04 +0800
committerSasha Levin <alexander.levin@verizon.com>2017-09-10 10:59:17 -0400
commite6d5242aac71d8737acde0c39bb08cb504b77471 (patch)
treecf8a8564d4ff94f2f303dd760343f1fc62656ed3 /arch
parent56b204ee5e4215c5beb8d28655d8bab9f0abc323 (diff)
Raid5 should update rdev->sectors after reshape
[ Upstream commit b5d27718f38843a74552e9a93d32e2391fd3999f ] The raid5 md device is created by the disks which we don't use the total size. For example, the size of the device is 5G and it just uses 3G of the devices to create one raid5 device. Then change the chunksize and wait reshape to finish. After reshape finishing stop the raid and assemble it again. It fails. mdadm -CR /dev/md0 -l5 -n3 /dev/loop[0-2] --size=3G --chunk=32 --assume-clean mdadm /dev/md0 --grow --chunk=64 wait reshape to finish mdadm -S /dev/md0 mdadm -As The error messages: [197519.814302] md: loop1 does not have a valid v1.2 superblock, not importing! [197519.821686] md: md_import_device returned -22 After reshape the data offset is changed. It selects backwards direction in this condition. In function super_1_load it compares the available space of the underlying device with sb->data_size. The new data offset gets bigger after reshape. So super_1_load returns -EINVAL. rdev->sectors is updated in md_finish_reshape. Then sb->data_size is set in super_1_sync based on rdev->sectors. So add md_finish_reshape in end_reshape. Signed-off-by: Xiao Ni <xni@redhat.com> Acked-by: Guoqing Jiang <gqjiang@suse.com> Cc: stable@vger.kernel.org Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions