I have added a 4th disk to my RAID5 array in mdadm, and everything seems be OK after the resync. But I am unable to resize the volume.
The array is /dev/md0, and /dev/md0p1 is a partition thereof, and I think, this is what's causing the problems for me.
Trying to resize /dev/md0, unable to.
Code:
resize2fs /dev/md0
resize2fs 1.41.12 (17-May-2010)
resize2fs: Bad magic number in super-block while trying to open /dev/md0
Couldn't find valid filesystem superblock.
Then I tried /dev/md0p1
Code:
resize2fs /dev/md0p1
resize2fs 1.41.12 (17-May-2010)
The filesystem is already 244192511 blocks long. Nothing to do!
cfdisk /dev/md0 gives me this, so the free space is available on md0!
(It says it is ext3 but it is ext4 though).
Code:
cfdisk /dev/md0
Disk Drive: /dev/md0
Size: 1500320366592 bytes, 1500.3 GB
Heads: 2 Sectors per Track: 4 Cylinders: 366289152
Name Flags Part Type FS Type [Label] Size (MB)
-----------------------------------------------------------------------------------------------------
md0p1 Primary Linux ext3 1000212.53
Pri/Log Free Space 500107.84
If I do a mount, and do an info,it says ext4.?
Code:
/dev/md0p1 ext4 917G 839G 33G 97% /mnt/RAID5array
Any ideas? As said earlier, I think that the partition /dev/md0p1 of /dev/md0 is what is causing the problems.
The disk have been added to /dev/md0 and grown to /dev/md0.