> Is that supposed to be common knowledge ? Well, perhaps not. However, the Ubuntu and Debian installers use UUIDs *only* for disks that don't already have other persistent names - devicemapper devices are always added to /etc/fstab with their symbolic name. It's only when adding a filesystem post-install, or when moving the filesystem around as you say was done here, that it becomes an issue.
I think this is an issue we should try to raise awareness of, but I'm not sure where the right place to do that is; I don't know of any obvious places in the Ubuntu documentation that cryptsetup is even discussed. > Cryptsetup and/or mountall could at least spit some kind of warning if > the unsupported case is encountered, at least if the boot process just > got stuck. This would require mountall to treat _unformatted device names specially, when in fact it currently doesn't know anything about cryptsetup (and it's best, design-wise, to keep it that way). It also would not account for other cases of filesystems changing paths - multipath comes to mind here. I realize this isn't very discoverable right now and understand where you're coming from, I just don't think it's a good idea for us to special-case this in the software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719563 Title: mountall: fatal error: cannot open /dev/mapper/crypthome_unformatted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
