![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
On Mon, Mar 30, 2015 at 10:46 AM, Oliver Neukum <oneukum@suse.de> wrote:
Hi,
I recently experienced a filesystem issue that forced me to use the rescue system and I saw two issues regarding mounting filesystems that seemed bad to them
1) swap space is mounted by UUID That is problematic. If your swap space is corrupted you use mkswap. There practically is no other option. Doing so, however, you change the UUID and your system comes up without swap pretty much without warning.
You can change it, right? Whatever default you chose someone will be unhappy with it.
That is really nasty if you need to do S4 later on. It seems to me that swap should be mounted by device name.
2) systemd while coming up will tell you that a certain UUID is unavailable and fails to boot.
That message is more less useless. You pretty much won't find the partition by UUID after you reboot into the rescue system because unless you have superhuman memory or take a photograph you will not have the UUID any more. And even if you had it, you won't find it for the same reason systemd failed to find it.
A useful message would tell me where the filesystem was to be mounted at.
It should say that mount unit failed because of missing prerequisite. Mount point is both encoded in mount unit name and can be looked up in mount unit properties. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org