<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 14, 2018 at 4:48 PM, Markus Rohwedder <span dir="ltr"><<a href="mailto:rohwedder@de.ibm.com" target="_blank">rohwedder@de.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p><font size="2">Once inodes are allocated I am not aware of a method to de-allocate them. This is what the Knowledge Center says:</font><br><br><i>"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><br><br><br></p></div></blockquote><div class="gmail_default" style="font-family:verdana,sans-serif"><img src="cid:ii_jh667rva1_1635e6e0244c525b" width="388" height="195"></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">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.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p></p><br><font size="2" color="#5F5F5F">From: </font><font size="2">KG <<a href="mailto:spectrumscale@kiranghag.com" target="_blank">spectrumscale@kiranghag.com</a>></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.<wbr>org</a>></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">14.05.2018 12:57</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[gpfsug-discuss] pool-metadata_high_error</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org" target="_blank">gpfsug-discuss-bounces@<wbr>spectrumscale.org</a></font><br><hr width="100%" size="2" align="left" noshade style="color:#8091a5"><div><div class="h5"><br><br><br>Hi Folks<br><br>IHAC who is reporting pool-metadata_high_error on GUI.<br><br>The inode utilisation on filesystem is as below<br>Used inodes - 92922895<br>free inodes - 1684812529<br>allocated - 1777735424<br>max inodes - 1911363520<br><br>the inode utilization on one fileset (it is only one being used) is below<br>Used inodes - 93252664<br>allocated - 1776624128<br>max inodes 1876624064<br><br>is this because the difference in allocated and max inodes is very less?<br><br>Customer tried reducing allocated inodes on fileset (between max and used inode) and GUI complains that it is out of range.<br></div></div><tt><font size="2">______________________________<wbr>_________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at <a href="http://spectrumscale.org" target="_blank">spectrumscale.org</a><br></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/<wbr>listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br></font></tt><br><br><br>
<p></p></div>
<br>______________________________<wbr>_________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/<wbr>listinfo/gpfsug-discuss</a><br>
<br></blockquote></div><br></div></div>