The ext3 way of journalling

From: Tuomo Valkonen
Date: Tue Jan 08 2008 - 11:07:53 EST



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, because the kernel has decided to corrupt the
superblock to indicate that it's been years since last file system
check. And obviously the crappy init system provides no simple way to
stop the checking, to put it in the background, or whatever. The FOSS
herd is totally concentrated on creating a WIMP idiot box -- a cheap
plastic clone of Windows -- instead of fixing such fundamental problems.
Windows, by the way, boots like a blaze compared to woeful Linux crap
(even without the very definition of pure shit: udev, which the crap
known as Linux practically requires these days).

A partial contributor to the slow fsck process is:

hde: ST3160023AS, ATA DISK drive
hde: applying pessimistic Seagate errata fix

# hdparm -t /dev/hde
/dev/hde:
Timing buffered disk reads: 48 MB in 3.01 seconds = 15.96 MB/sec

Thank you very much. The disk worked perfectly well without that "fix"
in earlier (2.2 or was it some 2.4?) kernels and, in Windows too. That
raw timing is worse than the _encrypted_ transfer rate I get from other
disks.

One should always indicate the version of software when complaining. Well,

$ uname -a
Linux noi 2.6.14 #1 PREEMPT Sun Oct 30 20:18:48 EET 2005 i686 GNU/Linux

I've tried upgrading, and failed: the megatonne monolith with a gazillion
hidden options (and totally worthless make oldconfig) is impossible to
compile these days, and the distros' stock kernel are utter and total crap
that load drivers in wrong order etc., and are difficult to configure
(demanding crap that demands udev to edit their initrds). Not to even
speak of the udev-demanding scsi-mapping insanity of SATA etc. devices
these days.

I've had it with Linux. It's no longer for power users. It's so complex
that it's only for idiot users that are content with the shoddy defaults,
and (paid) developers.

--
Tuomo

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