Date: Thu, 7 Jul 2022 11:30:20 +0200 From: Ronald Klop <ronald-lists@klop.ws> To: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org Subject: set timestamp from ZFS-root - (was: Re: RPI4 + ntpdate + unbound) Message-ID: <1d44f820-da80-8a65-ec5f-35632a7dd971@klop.ws> In-Reply-To: <YsVaNqwNAdlEoHdj@server.rulingia.com> References: <Yr/DPWc9Y%2Brp0J78@phouka1.phouka.net> <YsVaNqwNAdlEoHdj@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/6/22 11:47, Peter Jeremy wrote: > On 2022-Jul-01 21:02:05 -0700, John Kennedy <warlock@phouka.net> wrote: >> So I've got a RPI4 (no system time stored in NVRAM) that I did a stock >> type FreeBSD install on setting the time with ntpdate and the unbound >> DNS server (aiming for DNSSEC). As many people have noted before me, >> that setup is sort of broken because you can't look up DNSSEC hosts if >> you think it's 1970. No NTP time servers == no date reset == no DNS. > > If you're running UFS, the system clock should get set to the timestamp > in the superblock. That will be the last sync before the previous > shutdown so it'll be minutes to hours out of date but that should be > recent enough for DNSSEC to work. > > Note that this only works on UFS - see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254058 > > As an alternative option, the RTC in both the Rock64 and RockPro64 > are supported. > This is a nifty feature I did not know about. Cc-ing freebsd-fs@ to try get some attention on this. Is it possible to implement this on ZFS? Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1d44f820-da80-8a65-ec5f-35632a7dd971>