Date: Mon, 16 Jul 2007 16:57:20 +0700 From: Victor Snezhko <snezhko@indorsoft.ru> To: Ivan Voras <ivoras@fer.hr> Cc: David Malone <dwmalone@maths.tcd.ie>, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Debugging times Message-ID: <uwsx0k6wv.fsf@indorsoft.ru> In-Reply-To: <469B2787.9010302@fer.hr> (Ivan Voras's message of "Mon, 16 Jul 2007 10:08:39 %2B0200") References: <f6u94s$v6o$1@sea.gmane.org> <20070709214216.GA72912@walton.maths.tcd.ie> <f6ucs8$d6t$1@sea.gmane.org> <20070711132202.GA95487@walton.maths.tcd.ie> <uk5t1xa08.fsf@indorsoft.ru> <469B2787.9010302@fer.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Voras <ivoras@fer.hr> writes: >> Also, this was a surprise to an unexperienced me, but I have also >> found that vfs_mount initializes RTC with the latest timestamp found >> on local file systems - this explains why kernel "worked" for Ivan on >> a hard drive. It didn't actually work, but used timestamp which was >> stored on filesystem during unmount. > > Wow - this is just astonishing - why would a file system have anything > to do with the RTC? Sorry, some sloppy wording on my part. That was system clock, not RTC. The code which makes sure that system clock is initialized to root fs timestamp is in vfs_mount.c since 1.34. Initially it was commented as "sanity check". That might make some sense, although was a surprise to me. -- WBR, Victor V. Snezhko E-mail: snezhko@indorsoft.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?uwsx0k6wv.fsf>