Using the UUID in the fstab is wrong because it's racy. The individual
member devices appear at boot, and are exposed via udev, before the
system knows that they're part of a multipath set. And if systemd winds
up mounting the member instead of the mpath device, you get degraded
mounts without multipath redundancy.
The /etc/fstab needs to reference a device that is *unique* to the
system, will only appear once, and points to the multipath device.
I don't remember which is the right name schema to use for multipath
devices in particular - the mpathN-partM names may not be guaranteed to
be stable - but prior art in debian-installer for partman-multipath
should illuminate; or Matt may be able to provide some guidance.
** Changed in: subiquity
Assignee: Steve Langasek (vorlon) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: curtin (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847263
Title:
multipath installations generate incorrect fstab
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1847263/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
