Ext4 block / inode count wrong

[athare]

Hi guys,

I'm running a small development server on Ubuntu 10.04 server 64 bit with ext4 as the File system type.

I keep on getting wrong block / inode size when I do an fsck:

fsck -n /dev/sda1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
Warning!  /dev/sda1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda1 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 (3796179, counted=1684233).
Fix? no

Free inodes count wrong (8322533, counted=8319127).
Fix? no


/dev/sda1: ********** WARNING: Filesystem still has errors **********

/dev/sda1: 107035/8429568 files (0.2% non-contiguous), 29894957/33691136 blocks

I then force an fsck and the problem is solved, but given a day or two, the problem is back. This can sometime consume up to 10G of my HDD space.

df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             127G  121G     0 100% /
none                   16G  180K   16G   1% /dev
none                   16G     0   16G   0% /dev/shm
none                   16G   64K   16G   1% /var/run
none                   16G     0   16G   0% /var/lock
none                   16G     0   16G   0% /lib/init/rw
tmpfs                  28G   28G  618M  98% /extents
none                  127G  121G     0 100% /var/lib/ureadahead/debugfs

Notice the size, used and available on "/dev/sda1"

any idea what can be causing or how I could fix this?

[bclark4444]

Ext4 is still relatively new. You may want to take this to your distro's support forum so they can check their base and elevate it to the ext4 folks if necessary.

[Rubberman]

You are trying to run fsck on a mounted file system. Boot from a live/rescue CD/DVD/USB drive and try running fsck -f on the file system with it unmounted.

[athare]

I've run this from a live disc as well, it's finds and fixes the problem, but it returns again in a day or two. Also, using df -h I'm missing 6Gb of HDD space. Anyone know if this is reserved for something?

df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             127G  121G     0 100% /