NetApp volumes allow for inodes to be dynamically allocated/increased on volumes which are provisioned on an array. This begs the question, what is the maximum inode count supported by a volume and how is the maximum number calculated?
inodes = files
“The maximum number of inodes is limited to one inode per one block in the filesystem. (which is 1 inode per every 4KB). It is generally recommended to NOT go that low.”
1,288,490,189KB / 4KB Blocks = 322,122,547 supported files / inodes per 1.2TB volume.
Credit where credit is due… https://communities.netapp.com/thread/2176
NetApp virtual filers are handy for implementing multiple isolated environments which can have their own domain authentication and network isolation. In order to completely isolate a vFiler from a physical filers interfaces separate dedicated interfaces must be assigned. In the NetApp world interfaces are grouped based on IPSpaces. For each IPSpace there can only be one default gateway. By creating multiple IPSpaces you can isolate a vFilers storage traffic and also allow for multiple default gateways. The use of multiple default gateways removes the need for adding static routes to the physical filer and also precludes asymmetric routing issues from occurring.
Goal: Change the IPSpace of an existing vfiler without losing any of the existing configuration settings.
Note: You will need to recreate any local accounts previously created using the useradmin command.
Make a copy of the following files prior to attempting to change your vfilers IPSpace.
- \etc\exports (only if the filer serves NFS shares)
- \etc\cifsconfig_share.cfg (only if the filer serves CIFS shares)
- \etc\cifs_homedir.cfg (only if you use home directory mapping capability)
Active Directory Filer Association
Create the new VIF & IPSpace. Note that vifs which use LACP will initially come up but show as broken until an IP address is bound to it.
brain dump in progress…