rgbtxus
November 26th, 2008, 05:51 AM
I have a RAID5 array that currently is composed of 4 320GB partitions on 4 disks. This array is one of several physical volumes in a LVM volume group. I just upgraded to Intrepid (two days ago). And tonight installed the big update that was available today. So this problem occurs with the latest and greatest. I'm running out of space and so want to add a fifth disk. I have done this on several occasions to other arrays and so did not anticipate problems -- always a mistake.
mdadm --add /dev/md21 /dev/sdi1 worked like a champ and the drive was added uneventfully as a spare to md21. When I try mdadm --grow /dev/md21 --backup-file=/root/mdadmtmp -n 5 I get "mdadm: Cannot set device size/shape for /dev/md21: Device or resource busy" and dmesg shows "md: could not update array info. -16"
I've tried stopping nfs and samba (which share some of the files hosted on the PV), unmounting the logical volumes on the PV and setting the volume group inactive hoping that somehow LVM was the culprit. No dice. So I rebooted into rescue mode, drop to a root shell, unmounted and deactivated as above to no avail.
lsof /dev/md21 and /dev/sdi1 return no results. So who might be responisble for the "busy?" mdadm -D/-E of the relevant devices all look fine and consistent with this (sdi was removed before this, but was there)
/dev/md21:
Version : 00.90
Creation Time : Wed Nov 14 23:40:31 2007
Raid Level : raid5
Array Size : 937512768 (894.08 GiB 960.01 GB)
Used Dev Size : 312504256 (298.03 GiB 320.00 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 21
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Nov 25 23:20:38 2008
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 5bf98f0f:38057634:dafc93a3:f3c76e1e
Events : 0.9026
Number Major Minor RaidDevice State
0 8 113 0 active sync /dev/sdh1
1 8 97 1 active sync /dev/sdg1
2 8 65 2 active sync /dev/sde1
3 8 81 3 active sync /dev/sdf1
I'm getting really tight on space so could really use some help here (wiping, recreating and reload would be a major PITA since this PV is but one that support the LVs)
TIA
****
mdadm --add /dev/md21 /dev/sdi1 worked like a champ and the drive was added uneventfully as a spare to md21. When I try mdadm --grow /dev/md21 --backup-file=/root/mdadmtmp -n 5 I get "mdadm: Cannot set device size/shape for /dev/md21: Device or resource busy" and dmesg shows "md: could not update array info. -16"
I've tried stopping nfs and samba (which share some of the files hosted on the PV), unmounting the logical volumes on the PV and setting the volume group inactive hoping that somehow LVM was the culprit. No dice. So I rebooted into rescue mode, drop to a root shell, unmounted and deactivated as above to no avail.
lsof /dev/md21 and /dev/sdi1 return no results. So who might be responisble for the "busy?" mdadm -D/-E of the relevant devices all look fine and consistent with this (sdi was removed before this, but was there)
/dev/md21:
Version : 00.90
Creation Time : Wed Nov 14 23:40:31 2007
Raid Level : raid5
Array Size : 937512768 (894.08 GiB 960.01 GB)
Used Dev Size : 312504256 (298.03 GiB 320.00 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 21
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Nov 25 23:20:38 2008
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 5bf98f0f:38057634:dafc93a3:f3c76e1e
Events : 0.9026
Number Major Minor RaidDevice State
0 8 113 0 active sync /dev/sdh1
1 8 97 1 active sync /dev/sdg1
2 8 65 2 active sync /dev/sde1
3 8 81 3 active sync /dev/sdf1
I'm getting really tight on space so could really use some help here (wiping, recreating and reload would be a major PITA since this PV is but one that support the LVs)
TIA
****