| Summary: | External drives with swaps are automatically added to fstab which may slow boot when drive is unplugged. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jeff Robins <jeffrobinsSAE> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools | CVE: | |
| Status comment: | |||
|
Description
Jeff Robins
2013-01-12 18:37:13 CET
Manuel Hiebel
2013-01-21 22:44:28 CET
Assignee:
bugsquad =>
mageia systemd does not automatically add any swaps to /etc/fstab. It will never edit your fstab for you. So something else is adding the device to fstab. systemd considers things you add to fstab to be required components of boot. If you don't want it to fail and drop you to an emergency shell when the fstab entry does not exist, then you need to add the "nofail" mount option. So I'm not sure what is automatically adjusting fstab but I'd suggest that it should default to adding the nofail option to any swaps it adds. I'm not sure what component adds swaps to fstab, but I'm guessing some kind of harddrake stuff. Source RPM:
systemd =>
drakxtools
Colin Guthrie
2013-01-27 14:37:27 CET
Summary:
Systemd automatically adds swap to fstab and then pauses for a long time when it is missing =>
External drives with swaps are automatically added to fstab which may slow boot when drive is unplugged. I repeated the experiment with a similar drive** and I could not reproduce the problem. I even went to "Manage disk partitions" in the MCC just to see if maybe I had done that before and forgot, but it didn't cause the problem either. As far as I could determine nothing ever altered fstab and the computer had no problems upon subsequent boots. The sda/sdb ordering where still switched but I'm going to blame that on the motherboard. I'd close this but I can't find an option for cannot duplicate. --Jeff **I was backing up the files on a laptop before it went in for repairs. Apparently the hard drive failed some of their tests so they scrapped it and installed a new one, but didn't copy the contents to the new drive. I don't know what size the partitions were or the order, so I can't do an exact test. The hard drive wasn't the reason the laptop went in, so I wasn't expecting them to scrap it. "WORKSFORME" is the closest resolution for to "Cannot duplicate". FWIW, the swapping of sda and sdb is pretty much expected. Many different things can happen in the kernel to affect the ordering of such things (e.g. loading the USB kernel module before the kernel module for your SATA controller or vice versa. This is why, for many years now, we've always defaulted to partition UUIDs in our fstab entries and kernel command lines. Status:
NEW =>
RESOLVED |