Re: The ext3 way of journalling

[Tuomo Valkonen <tuomov@iki.fi>]

On 2008-01-12 10:06 -0500, Theodore Tso wrote:
> So running the "date" command after the boot sequence is completely
> finished.  That doesn't mean that system clock was correct at the time
> when fsck is run.  

Unless ntpd has managed to change it by that time, it was correct, 
in the local time zone. But judging from the "too big difference,
refusing to correct" behaviour of ntpd while the system is up,
I doubt ntpd would correct the time at boot, if it were considerably
wrong. This rapidly advancing system clock is A COMPLETELY DIFFERENT
PROBLEM that started with switch from 2.6.7 to 2.6.14. Before that
it worked just fine.

> Unfortunately Ubuntu users in Europe fit this
> demographic hugely, and Ubuntu refuses to fix this problem[1], so it's
> been personally very vexing, because the users complain to *me*, and I
> can't fix the problem, because it's a distribution init script issue.

FYI, I'm not running Ubuntu. This system once used to by Debian, 
but since Etch is already obsolete wrt. many non-base software, 
and I'm not going to suffer stable/unstable anymore, and megafrozen
megadistros with everything between the earth and skies suck anyway,
largely consists of self-installed software by now. Maybe they broke
time initialisations for etch.

Also, I must say that e2fsck is brain-damaged, if it can be confused 
by/do the stupid then when the system clock has warped by just a few
hours, not the _days_ that a file system check interval typically is,
and users need to specifically kludge around such misbehaviour in 
e2fsck.

-- 
Tuomo