> OK, so your new array size will be 5857612608 (1952537536 * 3) == 5586GB
>
> You can use an initial resize2fs to 5.4T to speed things up, as you don't really need to move items that are currently located between the 3.8T and 5.4T mark. ÂThen use the exact "mdadm --grow /dev/md0 --array-size=5857612608" afterwards before you fsck it.
>
> If that passes, do the rest. ÂThe final resize2fs should be very quick.
>
> Phil
>
One more glitch? I ran the following command, trying several different
locations for the backup file, all of which have plenty of space and
are not on the array.
sudo mdadm -G /dev/md/0_0 -n 4 --backup-file=/tmp/backmd
mdadm gives the message "mdadm: Need to backup 960K of critical
section.." and it immediately returns to the command prompt without
shrinking the array.
Following is the current array info
ubuntu@ubuntu:~/mdadm-3.2$ sudo mdadm -D /dev/md/0_0
/dev/md/0_0:
Version : 0.90
Creation Time : Thu Jan 6 06:13:08 2011
Raid Level : raid5
Array Size : 5857612608 (5586.25 GiB 5998.20 GB)
Used Dev Size : 1952537536 (1862.08 GiB 1999.40 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 127
Persistence : Superblock is persistent
Update Time : Sun Mar 13 06:46:37 2011
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 7e946e9d:b6a3395c:b57e8a13:68af0467
Events : 0.73
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 50 1 active sync /dev/sdd2
2 8 66 2 active sync /dev/sde2
3 8 82 3 active sync /dev/sdf2
4 8 98 4 active sync /dev/sdg2
5 8 114 5 active sync /dev/sdh2
--
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
