Hmmm.... simply changing the status to invalid just doesn't solve the issue.
I outlined above how to reproduce this bug. Clone a partiton, give it a new label and UUID, and blkid yields nonsense. This did not go away. Ubuntu has moved to UUID-based mounting (which is a controversial issue in itself) , so the user tools to write an ubuntu-compliant fstab should work reliably. So even if a partition had a filesystem previously, there needs to be correct filesystem information given back to the user, may it be a udev- or a blkid-bug. -- Different UUID between udev and fstab https://bugs.launchpad.net/bugs/110251 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
