Tom,
Just a w.a.g., but (vol in k) / 4 = maxfiles, I think.
Hmmm, though. The numbers don't quite match.
statler> df -i /vol/spool Filesystem iused ifree %iused Mounted on /vol/spool/ 190362 4809618 4% /vol/spool/ statler> df /vol/spool Filesystem kbytes used avail capacity Mounted on /vol/spool/ 31776308 6277576 25498732 20% /vol/spool/ /vol/spool/.snapshot 0 5920 0 ---% /vol/spool/.snapshot statler> Connection closed by foreign host. bash-2.02# expr 31776308 / 4 7944077 bash-2.02# expr 190362 + 4809618 4999980 bash-2.02#
So spool is not at max inodes.
statler> maxfiles spool Volume spool: maximum number of files is currently 4999980 (190363 used). statler> maxfiles spool 999999999 Max inode count cannot exceed 8385415 statler>
bash-2.02# expr 8385415 * 4 33541660 bash-2.02#
not 31776308.
Dave
Tom "Mad Dog" Yergeau wrote:
Hi,
I know filers by default won't get a volume more than, say, 33 million inodes, and that the general formula for determining the number of inodes is (volume size in kilobytes) / 32 kb = #of inodes.
But, does anyone know if there is a maximum number of inodes? Does anyone out there have volumes with over 200 million inodes and have you seen any issues with those types of volumes?
We've got an application that's generating about 5-10 million inodes a month (don't ask) and I'm concerned about that. Will this be a problem?
Thanks! Tom