xfs dynamically allocates inodes, up to some maximum percentage of disk
space - that's the imaxpct you see in the mkfs output below.
df -i reports as total inodes the number which -could- be allocated.
You can reduce this with xfs_growfs:
[root@lite ~]# df -i /mnt/sda1
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda1 2008064 5 2008059 1% /mnt/sda1
[root@lite ~]# xfs_growfs -m 1 /mnt/sda1
xfs_growfs: ignoring entry /eric1s0 in /etc/mtab: Stale NFS file handle
meta-data=/mnt/sda1 isize=256 agcount=8, agsize=62752 blks
= sectsz=512
data = bsize=4096 blocks=502016, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=2560, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
inode max percent changed from 25 to 1
[root@lite ~]# df -i /mnt/sda1
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda1 80320 5 80315 1% /mnt/sda1
-Eric
Tim Flower wrote:
My question is this. Is there anything that can be done on the
server-side to influence the free inodes/files that XFS reports?
(Specifically, other than rebuilding the XFS partition smaller)
Also a related question, has anyone ever run into this sort problem in
the past and (if so) what did you do to work around it?
|