Filesystem corruption

This seems to be an exceptionally good week!

Like it isn’t enough with the router hanging randomly, the filesystem on the the server seems to be breaking. I’ve got lots of

Jul 26 06:26:33 ismo kernel: [212657.328000] init_special_inode: bogus i_mode (36163)
Jul 26 06:26:33 ismo kernel: [212657.504000] init_special_inode: bogus i_mode (30060)
Jul 26 06:26:35 ismo kernel: [212658.952000] init_special_inode: bogus i_mode (74564)
Jul 26 06:26:35 ismo kernel: [212658.952000] init_special_inode: bogus i_mode (71541)
Jul 26 06:26:41 ismo kernel: [212664.840000] init_special_inode: bogus i_mode (74063)
Jul 26 06:26:41 ismo kernel: [212665.432000] init_special_inode: bogus i_mode (31045)

lines in my syslog files. More exactly

/var/log# zgrep init_special_inode syslog* | wc -l
109

109 lines. Starting on the 20th of July. This is with the latest ubuntu release:

Linux ismo 2.6.20-16-386 #2 Thu Jun 7 20:16:13 UTC 2007 i686 GNU/Linux

Hmm, looking more closely it seems I get the output at the same time every day. Seems like it’s logwatch that is triggering the error! If I’m lucky it might be that it’s just one of the log files that are broken.