raid1 creation problems

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

 



why would mdadm be creating a md device (raid1) that was larger than the partition table?
these are two identical seagate 120's --debian 2.4.26 with raid compiled in.
i have built the partition tables with fdisk cfdisk and parted same problem everytime . everything is fine
up until i boot at which time it say's the superblock is larger than the partition by about 20 or 30 blocks
I have built several other raid1 system's over the last year and have not seen this problem before.
to add the drives to the array i boot under a recuse disk and sync under the rescue disk. same mdadm
version as they were built with. The partition tables match in all cases -- with fdisk i kept everything on cyl
boundaries.


where and how does mdadm check partition size?
thanks
rob


-
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