linux-kernel - Re: The ext3 way of journalling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080114111158.GB29126@jolt.modeemi.cs.tut.fi>
Date:	Mon, 14 Jan 2008 13:11:58 +0200
From:	Tuomo Valkonen <tuomov@....fi>
To:	Bernd Petrovitsch <bernd@...mix.at>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

On 2008-01-14 10:57 +0100, Bernd Petrovitsch wrote:
> That leads to the question why the clock starts to run like crazy at
> some time so that `ntpd` can't cope with it.

I do wonder whether the PSU could've been causing it. Now that think
about it, I got the PSU around two years ago, just like I compiled 
2.6.14. This PSU coincidentally seems to have been the cause of the 
crash that started this thread, and went completely silent during 
the same day, on the third crash. But even if the PSU could cause
the timer interrupt to signal too frequently or so, doesn't explain
why nearly always after a crash (when journal recovery would be the
normal course of action), fsck starts checking with absurd intervals
since last check, whereas there's no trouble booting after normal
shutdown.

-- 
Tuomo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/