summaryrefslogtreecommitdiff
path: root/drivers/md
diff options
context:
space:
mode:
authorMarkus Hochholdinger <markus@hochholdinger.net>2021-11-16 10:21:35 +0000
committerSong Liu <song@kernel.org>2021-12-10 09:11:07 -0800
commit55df1ce0d4e086e05a8ab20619c73c729350f965 (patch)
treeca62fc911c139aa8752eb8f304c11d33e685f975 /drivers/md
parent091f06d91cbc8a51b63c26007e29baae49282b16 (diff)
md: fix update super 1.0 on rdev size change
The superblock of version 1.0 doesn't get moved to the new position on a device size change. This leads to a rdev without a superblock on a known position, the raid can't be re-assembled. The line was removed by mistake and is re-added by this patch. Fixes: d9c0fa509eaf ("md: fix max sectors calculation for super 1.0") Cc: stable@vger.kernel.org Signed-off-by: Markus Hochholdinger <markus@hochholdinger.net> Reviewed-by: Xiao Ni <xni@redhat.com> Signed-off-by: Song Liu <songliubraving@fb.com>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/md.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 5111ed966947..e97d2faf1e88 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -2189,6 +2189,7 @@ super_1_rdev_size_change(struct md_rdev *rdev, sector_t num_sectors)
if (!num_sectors || num_sectors > max_sectors)
num_sectors = max_sectors;
+ rdev->sb_start = sb_start;
}
sb = page_address(rdev->sb_page);
sb->data_size = cpu_to_le64(num_sectors);