This has happened quite a few times to me. Coming from an EDA environment as well, it's not uncommon for relatively small volumes to have huge numbers of files (20 million files on a 450GB volume).
maxfiles is what I use, typically adding a million files at a time. I'm not exactly sure what the algorithm Netapp uses to add inodes as you increase volume size, so I just take the more direct route. Plus I don't want to just throw space at engineers who will consume it "just because." Remember, after adding inodes, you can't decrease the number and they consume space from the volume.
-- /* wes hardin */ UNIX System Admin Dallas Semiconductor/Maxim Integrated Products
Magnus Swenson wrote:
Hello Toasters,
Just wanted to do a quick check, what the standard practise is when running out of inodes on a volume.
I have several flex volumes in one aggregate. One of the volumes only at 80% full ran out of inodes.
df -i will show number of inodes used and inodes free.
This is a 100G volume with 3458831 inodes.
According to now.netapp.com, there are two solutions,
increase inodes with the 'maxfiles' command, or add more disk space to the volume.
Has anybody had experience with this and which way did you go?