Ralf Müller <ralf@xxxxxxxx> writes:
> After I added a forth 1.5TB disk to the array yesterday and reshaped the
> former 3 disk raid5 to a 4 disk one, I wiped out the 300GB disk raid5,
> set one
> of the 1.2TB partitions faulty, removed it from its raid, removed the
> 300GB
> partition and resized the former 1.2TB partition (in place) to
> 1.5TB. Now I
> added this partition to its raid.
>
> It has been recognized as a former member of this raid - so far so
> good - but
> for whatever reason the raid subsystem decided to start a complete
> recovery.
> So here my question:
>
> What went wrong and what do I have to do to avoid a full recovery for
> the
> next disk?
I guess something wrote to your raid5 while the one disk was
removed. When you added it back the event counter would differ and the
disk needs to be resynced completly. A bitmap would help limiting this
to the parts that have changed. Add an internal bitmap before you
remove the next disk.
Alternatively stop the raid completly, resize all the partitions and
start the raid again. No need to fail/readd each disk in turn.
> I do not feel well with a degraded raid5 in a 10 hour rebuild ...
>
> Regards
> Ralf
MfG
Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
