Matthew Dillon wrote: > > The question is whether we can simply require that vinum partitions > skip the label area (i.e. the starting block has to be at least 16 > for a partition created with a normal disklabel) or whether there > are backwards compatibility issues that require us to support vinum > writing into the disk's label area. >
More seriously, I'm not sure if an existing configuration would be forwards-compatible anyway due to the new label changes if someone had used 'raw' slices, etc. Although having to shift the on-disk filesystem layout for upgrade is a different kind of animal compared to a 'dumpconfig', 'edit slice cfg in file' 'recreate vinum setup' kind of a change, especially if you have lots of data on the drives and have to copy it elsewhere to do the shift I don't have anything setup with a vinum root disk, so not sure if that is working / related to this portion of the code or not. Hopefully I'll get around to testing vinum boot one day, but it hasn't arrived yet .. Without knowing what the in-boot2-location code does thats probably all I can say without spewing (more :) hot air onto the topic.. I suppose that's a brainstorm for possible impact.. - Chris
