Re: [ANNOUNCE] mdadm-3.1 has been withdrawn

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

 



On Thu, 12 Nov 2009, Bill Davidsen wrote:

I like 1.2, I feel it's least likely to suffer collateral damage, and the problems it causes seem to result in the type of behavior you mention aboue, the system says "Can't, won't, you don't know what you're doing."

What about adding a new v1.3 superblock which basically has 4 superblocks, an old 1.x superblock residing at <end>-<v1.0 superblock size> (new location), and then pointers to this block residing where 1.0, 1.1 and 1.2 superblocks would normally be? Wouldn't that solve "everybodys" problem by making it easier to find the superblock regardless of what might have happened (drive size changed because of 3ware, someone installed mbr on the drive etc).

--
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