filesystem not full, but 0% available

Colin van Niekerk Colin.vanNiekerk at
Fri Apr 3 14:19:08 UTC 2009

Hi there,

I would say this is probably because the normal behaviour when formatting partitions is to reserve 5% of the partition for UID 0 user (root) and GID 0 (root) group. The other partition is very much smaller so the effects of this would be much less noticeable.

If you take the number of reserved blocks and multiply them by the size of each block you get just a little more than 30GB.

Reserved block count:     8620077
Block size:               4096

The 'Available' column show the amount of space available to non-root users. Does the following command work?
Dd if=/dev/zero of=/mnt/sda3/testfile bs=1024 count=10000
This should create a 10MB file called /mnt/sda3/testfile and will let us know if root can still write data to the device.

Are these processes running as root?

Please could you provide the output of the following commands:
cat /etc/redhat-release
uname -a
ps -ef |egrep "syslog[d]|klog[d]"
ll `which klogd` `which syslogd`
mount |grep quota

Both these processes normally run as root, but it is possible to alter this behaviour so let's check these things.


-----Original Message-----
From: ext3-users-bounces at [mailto:ext3-users-bounces at] On Behalf Of peter pilsl
Sent: 03 April 2009 02:43 PM
To: ext3-users at
Subject: filesystem not full, but 0% available

I ran into a curious problem today:

Filesystem           1K-blocks      Used        Available Use% Mounted on
/dev/sda3            684172708     652718132       0      100% /mnt/sda3

While there should be 30GB available it shows that its full.  The partition is my /-partation and party of my linux ( thinks that this partition is really full.  Syslogd/Klogd are not working and /tmp is mounted as overflow-Ramdisk on boot.

I did a forced fsck twice by now, and I booted into a brand new 2.6.28-11-kernel and ext2-tools version 1.41.4 and the same problem.

Whats going on here? Anything left I can to debug or solve this problem? Next step is to backup all data on the disk, reformat the partition and restore the files, but actually this is not what I like to do on a regular base :)

fdisk does not complain about any harddisk/partition-troubles :
# fdisk -l /dev/sda

Disk /dev/sda: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00083824

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        4863    39062016   83  Linux
/dev/sda2            4864        5349     3903795   82  Linux swap / Solaris
/dev/sda3            5350       91201   689606190   83  Linux

and there is a second ext3-partition on the same disk (sda1) which doesnt have any similar problem. 

Would removing and adding the journal help? (I did this once but I cant remember why and especially how I did it)

Any help greatly appretiated,
I add the result of tune2fs -l /dev/sda3 at the end of this posting. Maybe it helps.

thnx a lot,

# tune2fs -l /dev/sda3 
tune2fs 1.41.4 (27-Jan-2009)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          3098e1e4-e120-469e-9e7b-41c2bb730b8f
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              43106304
Block count:              172401547
Reserved block count:     8620077
Free blocks:              7863644
Free inodes:              40182634
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      982
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   256
Filesystem created:       Wed Jun 18 10:19:42 2008
Last mount time:          Fri Apr  3 12:21:20 2009
Last write time:          Fri Apr  3 12:21:20 2009
Mount count:              1
Maximum mount count:      34
Last checked:             Fri Apr  3 11:09:13 2009
Check interval:           15552000 (6 months)
Next check after:         Wed Sep 30 11:09:13 2009
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      3536ec11-ab59-45b4-a4a4-6f1a37901363
Journal backup:           inode blocks

Ext3-users mailing list
Ext3-users at

More information about the Ext3-users mailing list