[gpfsug-discuss] pool-metadata_high_error

[KG]

On Mon, May 14, 2018 at 4:48 PM, Markus Rohwedder <rohwedder at de.ibm.com>
wrote:

> Once inodes are allocated I am not aware of a method to de-allocate them.
> This is what the Knowledge Center says:
>
> *"Inodes are allocated when they are used. When a file is deleted, the
> inode is reused, but inodes are never deallocated. When setting the maximum
> number of inodes in a file system, there is the option to preallocate
> inodes. However, in most cases there is no need to preallocate inodes
> because, by default, inodes are allocated in sets as needed. If you do
> decide to preallocate inodes, be careful not to preallocate more inodes
> than will be used; otherwise, the allocated inodes will unnecessarily
> consume metadata space that cannot be reclaimed. "*
>
>
>
I believe the Maximum number of inodes cannot be reduced but allocated
number of inodes can be. Not sure why the GUI isnt allowing to reduce it.
​

>
> From: KG <spectrumscale at kiranghag.com>
> To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
> Date: 14.05.2018 12:57
> Subject: [gpfsug-discuss] pool-metadata_high_error
> Sent by: gpfsug-discuss-bounces at spectrumscale.org
> ------------------------------
>
>
>
> Hi Folks
>
> IHAC who is reporting pool-metadata_high_error on GUI.
>
> The inode utilisation on filesystem is as below
> Used inodes - 92922895
> free inodes - 1684812529
> allocated - 1777735424
> max inodes - 1911363520
>
> the inode utilization on one fileset (it is only one being used) is below
> Used inodes - 93252664
> allocated - 1776624128
> max inodes 1876624064
>
> is this because the difference in allocated and max inodes is very less?
>
> Customer tried reducing allocated inodes on fileset (between max and used
> inode) and GUI complains that it is out of range.
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>
>
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180514/66673c36/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26124 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180514/66673c36/attachment-0002.png>