Hi Nicholas

Am 23.07.26 um 19:55 schrieb Nicholas D Steeves:

You're inducing a UUID collision, and this was a fs corruption footgun
until the kernel introduced a check for it.  UUIDs are supposed to be
unique, by definition, and you need to wipefs -a $DEVICE to eliminate
this collision before the second mkfs.  I'm reassigning this bug to
fsarchiver, because it should be running wipefs before mkfs.  As an
asside, this is also best practices when changing filesystems.

How do I create a UUID collision if I use it again for the same underlying device?

I would understand your argument, if I used the UUID for a different device.

Interestingly, I see no such failures with mkfs.ext4 or mkfs.xfs.

Regards,
Michael

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to