[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c87 --- Comment #87 from Dr. Werner Fink <werner@suse.com> 2012-07-04 10:35:17 UTC --- (In reply to comment #86)
In case it wasn't noticed by reading my recent comments, this has been happening on _many_ systems (and for many years), all of which are multiboot, most of which include every currently supported openSUSE release, usually plus Factory, plus at least one out of support openSUSE release, plus at least one non-openSUSE Linux release from Fedora, Mandriva, Mageia, Knoppix, Debian, CentOS, Gentoo and/or Kubuntu, plus a primary partition with at least one of OS/2 or DOS and/or Windows, and
all but one or two of which (the only two running RAID) have
***** CMOS clocks set to local time *****
and NTP configured to start on boot. [...]
CMOS in local time without having an initrd which inform the kernel *before* any file system is touched (file system check and mount) is a no go as the time stamps are wrong. This because the kernel assumes that CMOS clock is in UTC and uses this for its internal system clock which has to be in UTC. Otherwise the local time in user space (even the user space in initrd) has a wrong clock. Compare this with http://en.opensuse.org/SDB:Configuring_the_clock The mkinitrd script creates a clock warp setup if the CMOS clock is not in UTC for multi boot environments. With this the kernels assumption on the CMOS clock is corrected and the user space in initrd has its correct local time back. This is a hard precondition before running fsck on the root file system and mounting the root file system afterwards. Otherwise the time stamps are not correct. Even with this setup the problem of DST switches twice a year can cause trouble as the CMOS clock has to be corrected by user its self *before* the system accesses the file system. It should be noted that no system around here has its CMOS clock in local time. Even the most private systems uses UTC in CMOS ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com