[CFC/CFT] large changes in the loader(8) code
Hiroki Sato
hrs at FreeBSD.org
Fri Jun 29 03:06:00 UTC 2012
Pawel Jakub Dawidek <pjd at freebsd.org> wrote
in <20120628230725.GB1438 at garage.freebsd.pl>:
pj> PS. We are discussing two totally different things here:
pj> 1. Is placing GPT on anything but raw disk violates the spec? I can
pj> agree that it does and I'm happy with gpart(8) growing a warning.
I agree that there is a sort of violation, but in practice most of
implementations which use GPT can recognize the backup header as long
as the primary one is not corrupted by using the alternative LBA
field.
One thing we have to consider is what happens when the primary header
becomes broken. In that case and if a GEOM metadata is placed at the
end of the raw disk, GPT will be lost and it cannot recover by
non-GEOM-aware software including BIOS and other OS. Also, even for
FreeBSD it causes a boot failure. The modification which ae@
proposes mitigates this case. Of course, maybe BIOS or EFI will not
recognize the corrupted header because the backup header is not
located at the end. In that case all of the partitions are not
recognized and the FreeBSD does not boot. This is the trade-off when
we use GPT in a logical volume provided by GEOM. In short, the risk
is that backup header does not work as a backup when the primary is
broken. I agree that putting a warning about that is good and
enough. Whether this risk is acceptable or not depends on the
sysadmin. Also, we can describe the pros and cons in detail in a
section of the handbook because I and wblock@ are working on updating
it.
pj> 2. How to do software mirroring. Besides trying really hard I'm not sure
pj> what alternative are you proposing. Could you be more specific and
pj> describe how gmirror should be implemented in your opinion?
I do not think this topic is related to ae@'s change and this should
be discussed in a separate thread. His change aims to support a
non-standard GPT header location in a quite limited situation, not
actively promote such a configuration. The issue of GPT+GEOM is not
limited to gmirror. Just putting GEOM::LABEL metadata causes the
same issue.
-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20120629/800fd4cc/attachment.pgp
More information about the freebsd-hackers
mailing list