Hi John, thanks for your report, however...
* John Goerzen <[email protected]> [200512 20:24]: > There are multiple issues reflected in this report: > > 1) That mount failed to properly mount a filesystem; > > 2) That it incorrectly said it had mounted it; > > 3) That running systemctl daemon-reload fixed the issue; > > 4) That neither the mount nor the fstab manpages mentioned this interaction I must say this is a very generic report. To your points 1) and 2) I could ask "What did the kernel say at this time, esp. did it claim success?", to 3) and 4) I could say "There is also no documentation on interactions with other tools changing global system state, like reboot(1)". Now, none of these replies would be very helpful. I agree that generally requiring running "systemctl daemon-reload" after changing /etc/fstab would be bad. However that doesn't appear to be true in general. - Do you have specific reproduction steps, strace output or similar debugging information? I would hope these would be helpful to decide if this is a mount, udev, or kernel issue. - Does this still happen with 2.35.1-5? - What exactly do you want to see changed, and what are your wording suggestions? Thanks, Chris
