diff options
| author | NeilBrown | 2013-06-26 11:55:20 +1000 |
|---|---|---|
| committer | NeilBrown | 2013-06-26 12:38:19 +1000 |
| commit | eea136d69f9facb2d3807386bbac1e6b1161795f (patch) | |
| tree | bad385398a19c3c91774d2c85fd72842deb3944a | |
| parent | 725d6e579f06360744fc101b1af2f82d8aa282f1 (diff) | |
md: fix buglet in RAID5 -> RAID0 conversion.
RAID5 uses a 'per-array' value for the 'size' of each device.
RAID0 uses a 'per-device' value - it can be different for each device.
When converting a RAID5 to a RAID0 we must ensure that the per-device
size of each device matches the per-array size for the RAID5, else
the array will change size.
If the metadata cannot record a changed per-device size (as is the
case with v0.90 metadata) the array could get bigger on restart. This
does not cause data corruption, so it not a big issue and is mainly
yet another a reason to not use 0.90.
Signed-off-by: NeilBrown <neilb@suse.de>
| -rw-r--r-- | drivers/md/raid0.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c index fcf65e512cf5..c4d420b7d2f4 100644 --- a/drivers/md/raid0.c +++ b/drivers/md/raid0.c @@ -597,6 +597,7 @@ static void *raid0_takeover_raid45(struct mddev *mddev) mdname(mddev)); return ERR_PTR(-EINVAL); } + rdev->sectors = mddev->dev_sectors; } /* Set new parameters */ |