Originally posted by gens
View Post
As an example in this case take a program/script that takes files as input and outputs them elsewhere.Imagine you have a script that mirrors your /mn/music folder(which is a mounted external drive) to your google drive account. A failed mount in this case will result in nuking your online copy since your script will find an empty folder and mirror that "change" to your online space(which is intentional, if i delete a song from my PC i want it gone from my cloud). With systemd's interpretion of the fstab it correctly assumes that the failed mount of the external drive is a critical error and further booting the system will only make the problem worse, which again would be correct in this case. While the actual files on the external drive would be safe, since it wasn't actually mounted, the real damage in this example would be having to upload potentially hundreds of GB of data again.
The init system simply has no way to know which failed boot will mess up data somewhere and which won't. Unless you tell it by specifing no-fail that is.
Comment