[Bug 254058] zfs doesn't set mnt_time aka RootOnZFS doesn't work without RTC
[email protected] Fri, 05 Jun 2026 21:55:07 +0000
| Newsgroups | gmane.os.freebsd.devel.file-systems |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254058 Vincent Milum Jr <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Vincent Milum Jr <[email protected]> --- Just as an update: this bug still exists in all current FreeBSD branches. I've actively hit this bug during the development of Stratipi, but was unaware of this particular bug report, so I ended up making my own work-around for it. This is specific to my deployment, since it is for ensuring Chrony initializes correctly: https://github.com/circuitrewind/stratipi/blob/main/stratipi/usr/local/etc/rc.d/save_time So this issue isn't just annoying, it is actively a problem when using Chrony instead of ntpd. Chrony has a hard cap of ~50 years prior to compile time that it'll allow the system clock to jump from. Here in 2026, that means the earliest supported clock it can jump from is ~1976, 6 years after the default 1970 UNIX Epoch. Even with active upstream NTP servers, and even with a GPS clock source, Chrony will refuse to jump the system clock on such a large gap. -- You are receiving this mail because: You are the assignee for the bug.