Comment 1 for bug 395864

I have similar problems only on my disk this point is already reached at 30%.

If I do a '# debugfs /dev/md1' stats I see that there are only a few inodes left so I suspect that during the upgrade to Karmic's ext4 file system far too less inodes were created.

Does anyone know how to increase them without loosing data?

# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md1 493G 142G 346G 30% /

cp: cannot create directory `./Yazoo': No space left on device

# debugfs /dev/md1

stats

Filesystem volume name: main
Last mounted on: /
Filesystem UUID: 20423a23-b921-41b1-82bf-e27a826dd64d
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 504320
Block count: 129090240
Reserved block count: 1290902
Free blocks: 92021041
Free inodes: 35