A note to employers .

Nice reading, beginning of the post is quite similar to "Time management for System administrators " intro text. Geeks live and breathe "geek". 🙂 

If you’re running Debian Sarge, have a >2TB ext3 volume and your fsck.ext3 exits with signal 11 leaving the damn thing all dirty and stuff, get 1.39+1.40-WIP from backports.org . This fixed the problem for me on my home box (2.4T) and one of the servers here at work (4.7T). Takes a long while to fsck, but at least it gets through instead of crashing somewhere half way!

– ext2 doesn’t have a journal 

– ext3 is so "default". AND it gets b0rken just as well; on my home fileserver there were errors and fsck.ext3 exited with a SIGSEGV. Yikes. Upgrading to the 1.39-1.40 release from Sarge backports made that go away, luckily, but it’s still icky that it just broke like that and kept on humming along at the same time.

– XFS turned out to be really, really slow with many small files.

– ReiserFS only gave me corruption, headache and a murderer as an author 😉

– ZFS? Quoting Andrew Morton, "I haven’t seen a patch for that yet, but it’s very welcome!" 

What to do, what to do…