Description of problem: gfs_tool df reports the used inodes also as the total available inodes Version-Release number of selected component (if applicable): GFS-kernel-2.6.9-49.1.1 GFS-kernel-smp-2.6.9-49.1.1 GFS-6.1.5-0 How reproducible: gfs_tool fd <mountpoint of a GFS filesystem) Steps to Reproduce: 1. 2. 3. Actual results: Type Total Used Free use% ------------------------------------------------------------------------ inodes 114092 114092 0 100% metadata 447757 285678 162079 64% data 142735731 141006426 1729305 99% Expected results: df -i /data/climexp Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdc1 2005476 114092 1891384 6% /data/climexp Additional info:
The inode usage information shown by 'gfs_tool df <mountpoint>' is correct, but not terribly useful. For related discussion, see https://www.redhat.com/archives/linux-cluster/2006-January/thread.html#00131 inodes are created from metadata and data blocks. When inodes are destroyed, those blocks are reclaimed by the metadata and data block pools. That's why the free inode blocks is zero most of the time. Also, if you compare the output of 'df -i' with 'gfs_tool df', the free blocks (IFree) is basically the sum of free data and metadata blocks. IUsed is the number of inodes in use. We're looking to address this issue in future versions of gfs to present this information in a more useful manner.