Hello, Miroslav. You wrote 6 октября 2011 г., 16:59:19: > I am not a GEOM expert, but isn't it wrong concept, that glabel writes > its metadata and publish original device size? If some GEOM write > metadata at last sector (or first), then it should shrink the published > size (or offset). Or is the problem at geom_part, that it is writing > metadata past the advertised end of the device? Good point.
> e.g. If I have disk device with size of 100 sectors and glabel metadata > is stored at the last sector, then glabel should shrink the advertised > size to 99 sectors - then GPT secondary table will be at sector 99 > instead of 100. > The current state is simply wrong, because user can do something what > cannot work and is not documented anywhere. It is Ok in UNIX way, in general. You should be able to shoot your leg, it is good :) But if geom_label doesn't reduce its provider to count its own metadata, it looks like a bug! -- // Black Lion AKA Lev Serebryakov <l...@freebsd.org> _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
