Re: Shrinking raid array

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 12 Feb 2013, Phillip Susi wrote:

Yes, but the way it is now the superblock won't be found if the partition *is* resized. What is the use of reducing the amount of the partition mdadm is using if you can't then shrink the partition itself?

It makes sense if you for some reason want to use a smaller component drive (thinking mostly of older drives where 36 or 73GB didn't mean an exact size between manufacturers and you happened to create the array on a larger drive than you now have available.

Anyhow, I can see that what you're looking for is useful as well but I also believe it should be done through a special option and I imagine it should also output information regarding where the partition should now end (to use in fdisk) so mdadm can find the superblock next time.

--
Mikael Abrahamsson    email: swmike@xxxxxxxxx
--
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


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux