The usual cause is keeping your hardware clock in local time when your timezone 
offset is negative. Systemd initially checks /etc/fstab _before_ the system 
clock has been adjusted for the timezone offset. The solution is to keep your 
hardware clock in UTC, controlled by the third line in /etc/adjtime (see the 
manpage for adjtime-config).

--
Bob Nichols     "NOSPAM" is really part of my email address.
                Do NOT delete it.

On 2/16/23 04:45, Felix Miata wrote:
# mount <yada>
mount: (hint) your fstab has been modified, but systemd still uses
        the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
        the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
        the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
        the old version; use 'systemctl daemon-reload' to reload.
#

This recently started in F37 and continues with upgrades to F38. I make /any/
change to fstab, then reboot, and next attempt to mount anything manually that 
was
nofail or noauto in fstab, or had been mounted and I wish to remount, produces 
the
above messages, no matter how many boots have occurred since the actual fstab
edit. It used to be that a reboot constituted a systemctl daemon-reload, but 
that
seems to have disappeared. I found nothing on point in bugzilla. How does it 
track
what the old fstab contained, or that it changed when any change occurred one or
morer boots ago?

_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to