You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user Eric Herot(eherot) wrote on 2023-04-12T16:39:39.878935+00:00
This is legal in fstab:
LABEL=myvol /mountpoint ext4 defaults 0 0
It would be cool if cc_mounts would support mounting this way. It would also make mounting the correct EBS volume in the right place on EC2 a little more reliable, especially since fs_setup already supports applying a label.
Additionally, if mounts is unable to figure out how to resolve the filesystem identifier, perhaps it should just try to use it (and place it in fstab) anyway? Or at least have an option to "force" application instead of skipping it (and let the user deal with their non-booting instance).
The text was updated successfully, but these errors were encountered:
This bug was originally filed in Launchpad as LP: #2016030
Launchpad details
Launchpad user Eric Herot(eherot) wrote on 2023-04-12T16:39:39.878935+00:00
This is legal in fstab:
It would be cool if cc_mounts would support mounting this way. It would also make mounting the correct EBS volume in the right place on EC2 a little more reliable, especially since fs_setup already supports applying a label.
Additionally, if mounts is unable to figure out how to resolve the filesystem identifier, perhaps it should just try to use it (and place it in fstab) anyway? Or at least have an option to "force" application instead of skipping it (and let the user deal with their non-booting instance).
The text was updated successfully, but these errors were encountered: