On Mon, Mar 31, 2008 at 10:22:18PM +1100, NeilBrown wrote:
> On Mon, March 31, 2008 7:07 am, Shane W wrote:
> > Hello all,
> >
> > I had a three drive raid5 array of 750GB drives. Added a
> > fourth drive and grew the array but the actual size didn't
> > change.
>
> The size wont change until it finishes restriping. All the
> data needs to be relocated before the new space is available.
Ok this is the problem then. A drive failed during the
reshape so it got aborted so was running degraded with
three of four drives. Now that I've re-added the fourth,
it's showing as a spare rather than restarting the grow.
> What does "cat /proc/mdstat" show ??
continuum:~$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdd2[3] sdb2[0] sda2[2] sdc2[1]
152512 blocks [4/4] [UUUU]
md0 : active raid5 sdd1[4](S) sdb1[0] sda1[2] sdc1[1]
1464838528 blocks super 0.91 level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
bitmap: 32/175 pages [128KB], 2048KB chunk
> > Now when I do a mdadm --grow --size max /dev/md0,
> > I get:
> > mdadm: Cannot set device size/shape for /dev/md0: Device or
> > resource busy
>
> That is expected. The array is busy restriping (aka reshaping).
> You cannot change the size of individual devices at this time,
> not that you really want to.
> What is the current state of the array from /proc/mdstat?
Appears to be degraded but with a spare but not sure how to
bring the spare into the active array.
Shane
--
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
