On Thu, Apr 28, 2011 at 4:15 PM, Daniel Kalchev <dan...@digsys.bg> wrote: > > > On 28.04.11 01:30, Freddie Cash wrote: >> >> gmirror doesn't touch the start of the disk, but saves it's metadata >> in the last sector of the disk, and creates a new GEOM provider that's >> one sector shorter. >> >> GPT stores it's partition table in the first sector of the disk, and >> saves a backup copy of it in the last sector of the disk. > > This looks like layering issue to me. > > In theory, both gmirror and gpt should work on 'providers'. So if you give > an gmirrored provider to gpt it should touch the last sector of the gmirror, > but not the last sector of the disk - and not complain. It should not even > be able to see the last sector of the real disk. > > Is this hard to fix? >
I believe it goes like this gmX: | gpt | data | gpt | which in actual disk goes like this: adY: | gpt | data | gpt | gmirror | so geom read gpt in the first sector but doesn't find it in the last sector. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
