Re: Problem Growing Raid 5 Array - Help Needed!

[David Greaves <david@dgreaves.com>]

Jeremy Leigh wrote:
> Hi Guys, I have just grown my raid 5 from 7 to 8 500Gb drives.
> I am now running into this problem.
> When I try to run fsck /dev/md0 I get the following:

What command line?

> fsck.ext2: Device or resource busy while trying to open /dev/md0
> Filesystem mounted or opened exclusively by another program?
> 
> Or when I try to run resize2fs /dev/md0 to make use of new drive, I get the
> following:
> 
> resize2fs: Device or resource busy while trying to open /dev/md0
> Couldn’t find valid filesystem superblock.
again, what command.


> Cat /proc/mdstat outputs:
> 
> Personalities : [raid6] [raid5] [raid4] 
> md0 : active raid5 sdb1[0] sdi1[7] sdg1[6] sdh1[5] sdf1[4] sde1[3] sdd1[2]
> sdc1[1]
>       3418686208 blocks level 5, 256k chunk, algorithm 2 [8/8] [UUUUUUUU]
>       
> unused devices: <none>
So the resize worked and is complete.

> However, I can still access and mount my filesystem - I just cannot grow it,
> which I find very strange.
> I have tried to init 1, to go to single user mode, and I have made sure file
> system is unmounted, but this ‘busy’ error still occurs.

Have you rebooted? (Question, not suggestion)

What is the output from a mount command.
What is the line in /etc/fstab than normally mounts this filesystem?

Is mdadm running as a monitor daemon?

does lsof | grep <mountpoint> show anything?

David

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html