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]

Date:	Tue, 08 Jan 2008 17:53:13 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Tuomo Valkonen <tuomov@....fi>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

Tuomo Valkonen <tuomov@....fi> writes:

> The ext3 journalling code can be summarised as:
>
>     superblock->last_checked = random();
>     sync(superblock)
>
> I hate it: every time Linux crashes, e.g. due to power failure, it takes
> almost an hour to boot,

tune2fs -i0 -c0 device      for each file system

Yes that should be default, unfortunately it is not. It's one 
of the first things I do on new machines.

> Thank you very much. The disk worked perfectly well without that "fix"

fsck is actually seek bound, most likely it won't make much difference
for fsck. Seeky disk IO is always slow on a spinning disk.

There's actually been a patchkit recently to make fsck much faster
by clustering metadata better so it can be reached with less seeks,
but that hasn't reached mainline yet and and will unfortunately
require freshly created file systems.

-Andi
--
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/