When checking whether an existing filesystem matches the config, detect
multiple filesystem signatures on a target partition. If found, log a
warning. Don't do more than that for now, for backward compatibility
and because it's not clear that we should reject an otherwise-matching
filesystem just because it contains some leftover bits.
Disallow multiple signatures during test output validation, unless the
test requests otherwise.
libblkid always assumes sectors are 512 bytes, regardless of actual
size. Add detection for otherly sized sectors (e.g. 4k) and translate
the 512 byte values to logical-sector-sized values.
This commit adds two fields to the mount object in a filesystem: label
and uuid. With these changes, for filesystem reuse the label must always
match and the uuid must match if one is given in the config.
This adds the 'wipeFilesystem' flag to filesystem's 'mount' object. When
this flag is false, Ignition will inspect the current filesystem's type,
and reuse it if it matches the desired state. If this flag is true, the
current filesystem will always be reformatted when Ignition is run.
This is useful if the user wants to persist data across multiple runs of
Ignition.
This new flag can be safely used in conjunction with the deprecated
'force' flag. When both are set, the target filesystem is first checked
to see if it's the correct type. If so, the format operation is skipped.
If not, the 'force' flag determines if the existing filesystem (if any)
will be overwritten.
