If you receive this error on a NetApp volume, then it is an indication that the volume has a large number of files and that the volume has run out of inodes.
Here is how NetApp defines inodes.
The number of files a volume can contain is determined by how many inodes it has. An inode is a data structure that contains information about files. Volumes have both private and public inodes. Public inodes are used for files that are visible to the user; private inodes are used for files that are used internally by Data ONTAP. You can change only the maximum number of public inodes for a volume. You cannot affect the number of private inodes.
Data ONTAP automatically sets the maximum number of public inodes for a newly created volume based on the size of the volume: 1 inode per 32 KB of volume size. When the size of a volume is increased, either directly by an administrator or automatically by Data ONTAP through the autosize feature, Data ONTAP also increases (if necessary) the maximum number of public inodes so there is at least 1 inode per 32 KB of volume size, until the volume reaches approximately 1 TB in size. Growing the volume greater than 1 TB in size does not automatically result in more inodes, because Data ONTAP does not automatically create more than 33,554,409 inodes
You can use the command 'maxfiles' to find the inode consumption status.
filername> maxfiles cifs_vol1
Volume cifs_vol1: maximum number of files is currently 31876690 (31876690 used).
In order to resolve the issue, you can run the command 'maxfiles <volume name> <value>'
For ex:
filername> maxfiles cifs_vol1 40000000
The new maximum number of files will be rounded to 39999990.
filername> maxfiles cifs_vol1
Volume cifs_vol1: maximum number of files is currently 39999990 (31876690 used).
Here is how NetApp defines inodes.
The number of files a volume can contain is determined by how many inodes it has. An inode is a data structure that contains information about files. Volumes have both private and public inodes. Public inodes are used for files that are visible to the user; private inodes are used for files that are used internally by Data ONTAP. You can change only the maximum number of public inodes for a volume. You cannot affect the number of private inodes.
Data ONTAP automatically sets the maximum number of public inodes for a newly created volume based on the size of the volume: 1 inode per 32 KB of volume size. When the size of a volume is increased, either directly by an administrator or automatically by Data ONTAP through the autosize feature, Data ONTAP also increases (if necessary) the maximum number of public inodes so there is at least 1 inode per 32 KB of volume size, until the volume reaches approximately 1 TB in size. Growing the volume greater than 1 TB in size does not automatically result in more inodes, because Data ONTAP does not automatically create more than 33,554,409 inodes
You can use the command 'maxfiles' to find the inode consumption status.
filername> maxfiles cifs_vol1
Volume cifs_vol1: maximum number of files is currently 31876690 (31876690 used).
In order to resolve the issue, you can run the command 'maxfiles <volume name> <value>'
For ex:
filername> maxfiles cifs_vol1 40000000
The new maximum number of files will be rounded to 39999990.
filername> maxfiles cifs_vol1
Volume cifs_vol1: maximum number of files is currently 39999990 (31876690 used).
No comments:
Post a Comment