summaryrefslogtreecommitdiffstats
path: root/mdopen.c
diff options
context:
space:
mode:
authorPawel Piatkowski <pawel.piatkowski@intel.com>2023-10-19 16:35:25 +0200
committerJes Sorensen <jes@trained-monkey.org>2023-10-26 23:51:55 +0200
commitd8d09c1633b2f06f88633ab960aa02b41a6bdfb6 (patch)
treebc6c5cfb5ba70242a610199b36601974042967eb /mdopen.c
parentmdadm: remove container_enough logic (diff)
downloadmdadm-d8d09c1633b2f06f88633ab960aa02b41a6bdfb6.tar.xz
mdadm-d8d09c1633b2f06f88633ab960aa02b41a6bdfb6.zip
Fix assembling RAID volume by using incremental
After change "mdadm: remove container_enough logic" IMSM volumes are started immediately. If volume is during reshape, then it will be blocked by block_subarray() during first mdadm -I <devname>. Assemble_container_content() for next disk will see the change because metadata version from sysfs and metadata doesn't match and will execute sysfs_set_array again. Then it fails to set same component_size, it is prohibited by kernel. If array is frozen then first sign from metadata version is different ("/" vs "-"), so exclude it from comparison. All we want is to double check that base properties are set and we don't need to call sysfs_set_array again. Signed-off-by: Pawel Piatkowski <pawel.piatkowski@intel.com> Signed-off-by: Jes Sorensen <jes@trained-monkey.org>
Diffstat (limited to 'mdopen.c')
0 files changed, 0 insertions, 0 deletions