Magnus Thorne Magnus.Thorne@evoice.com writes:
NetApp has told me that they don't recommend that I have more than 250,000 inodes per volume.
Are you sure you're not confusing this with "per directory" ? Even though WAFL is fairly efficient when it comes to large directories, there are limits to what you would want to experience..
Is this a real limitation, because my NetApps currently have 6.1 million inodes available?
Neo, it's not. This is a 760:
df Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 343184120 265805356 77378764 77% /vol/vol0/ df -i Filesystem iused ifree %iused Mounted on /vol/vol0/ 13987164 6012814 70% /vol/vol0/
And it's running just fine (mailspool with one file per message)
The online documentation says I only need to add more hard drives to get more inodes (1 per 32K).
You can have 1 inode per 4K, IIRC.
Has anyone used the netapp for small files? Small means millions of < 60K. Also, I need all these files available on one share.
As you can see: yes, no problems.
Also, what should I look out for? I know to disable the read ahead cache.
I'm not sure that would help a lot with small files - this is more of a win wit large files (or possible very slow clients)
I plan to not use snapshots.
Whether or not to use snapshots is more a question of the change rate in your data set than the number of files - the 760 shown above is running with readahead set, and snapshots. No problems whatsoever.
Regards,