Re: GPT Table broken on a Raid1

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

 



On 23/09/2012 19:53, Chris Murphy wrote:
[...]
Upon creating a GPT on /dev/md/vol0, identical structures at identical byte offsets are created on /dev/sd[bc] and /dev/md/vol0.

The primary GPT header says the alternate header is at 0xffdfff.
The alternate GPT header is at 0xffdfff., or sector 16769023, right where it should be.

Regardless of whether the kernel sees the disk as Intel RAID or a bare disk, it finds the alternate GPT header, and doesn't complain about anything.

Yes, it does. It finds the alternate header just fine, according to the offset in the primary header, but warns that it's not at the end of the disc, which is where it expected to find it:

Sep 17 09:54:27 techz kernel: [    1.204681] GPT:Primary header thinks Alt.
header is not at the end of the disk.
Sep 17 09:54:27 techz kernel: [    1.204685] GPT:625137663 != 625142447
Sep 17 09:54:27 techz kernel: [ 1.204687] GPT:Alternate GPT header not at
the end of the disk.
Sep 17 09:54:27 techz kernel: [    1.204689] GPT:625137663 != 625142447

I know that's not what I said earlier, so my apologies for that, but it remains true that this is not a problem and there are no more GPT headers anywhere else on the disc than those written inside the IMSM volume.

Cheers,

John.

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