It is a 'feature'. XFS does not preallocate space for inodes at mkfs time
(ext2 for example does). Instead they are allocated on demand, but they are
never given back. So once you hit a high watermark with inode allocations,
you stay there and show up in the space used. In a filesystem which allocated
inodes at mkfs time I suspect the inode space is never included in the free
space reports.
Steve
> Hi
>
> I was testing xfs out, so i wrote a script that created 2.3 million files in
> a directory, they were zero lenth files, them i deleted them, but now the
> file system is using 500megs, i figure this is directory information that is
> being held for future use. But since i will not be using 2 million files on
> this file system, what is the best way to get this space back.
>
>
> here is some relavent information about my system
>
>
> [jamesd@magic jamesd]$ uname -a
> Linux magic 2.4.2-XFS #7 Mon Mar 12 23:26:54 CST 2001 i686 unknown
>
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda9 3.9G 580M 3.4G 14% /home4
>
>
> [jamesd@magic jamesd]$ df -i /home4
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/hda9 3.9M 3 3.9M 0% /home4
>
>
> please email if you need any further information
>
>
>
> Thank you
>
> James Dickens
>
>
|