One of my Ubuntu 10.04 servers is giving me trouble.
When I run
fsck.ext4 -n /dev/sda5 it tells me there are errors in the free inode count, free block count, and more.
I have tried:
shutdown -rF now
and still, after reboot, I see errors.
I also just checked on my eeePC netbook, Ubuntu 10.10, and have the same issue!
How can I force a really "forced" "forceful" "seriously fix my filesystem" fsck of the "/" filesystem on reboot?
Clarification: I run
fsck.ext4 -n because it's a mounted filesystem, to check if there are errors. This tells me that there are. I thought that the automatic fsck every 30 mounts during the boot-up process is precisely to take care of errors in the root filesystem. But it doesn't do it in my case.
I could reboot with a LiveCD and fix the errors, and then reboot again, but that's some serious downtime for a live server. A reboot, auto fsck, then continue booting is much more sustainable on a live server, and I believe should be the right behaviour.
Additional info: Here is the output. It looks like something that the autofsck would fix, doesn't it?
root@server:~# fsck.ext4 -n /dev/sda5 e2fsck 1.41.11 (14-Mar-2010) Warning! /dev/sda5 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/sda5 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (1849368, counted=1948909). Fix? no Free inodes count wrong (545504, counted=552134). Fix? no /dev/sda5: ********** WARNING: Filesystem still has errors ********** /dev/sda5: 116752/662256 files (0.2% non-contiguous), 795324/2644692 blocks