<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><div>-i will give you the exact used number but... Avoid running it during peak usage on most setups. It's pretty heavy, like running a -d on lssnapshot. </div><div><br></div><div>Your best bet is from earlier posts: '-L' gives you the max and alloc. If they match, you know you're in bother soon. It's not accurate, of course, but prevention is typically the best medicine in this case.</div><div><br></div><div>Cheers,</div><div>Barry</div><div>ArcaStream/Pixit</div><div><br>On 7 Aug 2015, at 21:12, Marc A Kaplan <<a href="mailto:makaplan@us.ibm.com">makaplan@us.ibm.com</a>> wrote:<br><br></div><blockquote type="cite"><div><font size="2" face="sans-serif">Try </font>
<br>
<br><font size="2" face="sans-serif"> mmlsfileset filesystem_name -i
<br>
</font>
<br>
<br><mime-attachment.gif>
<br>
<br>
<br>
<br><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">"Simon Thompson
(Research Computing - IT Services)" <<a href="mailto:S.J.Thompson@bham.ac.uk">S.J.Thompson@bham.ac.uk</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif">gpfsug main discussion
list <<a href="mailto:gpfsug-discuss@gpfsug.org">gpfsug-discuss@gpfsug.org</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">08/07/2015 12:49 PM</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: [gpfsug-discuss]
Independent fileset free inodes</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Sent by:
</font><font size="1" face="sans-serif"><a href="mailto:gpfsug-discuss-bounces@gpfsug.org">gpfsug-discuss-bounces@gpfsug.org</a></font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size="2"><br>
Hmm. I'll create an RFE next week then. (just in case someone comes back
with a magic flag we don't know about!).<br>
<br>
Simon<br>
________________________________________<br>
From: <a href="mailto:gpfsug-discuss-bounces@gpfsug.org">gpfsug-discuss-bounces@gpfsug.org</a> [<a href="mailto:gpfsug-discuss-bounces@gpfsug.org">gpfsug-discuss-bounces@gpfsug.org</a>]
on behalf of Rei Lee [<a href="mailto:rclee@lbl.gov">rclee@lbl.gov</a>]<br>
Sent: 07 August 2015 17:30<br>
To: <a href="mailto:gpfsug-discuss@gpfsug.org">gpfsug-discuss@gpfsug.org</a><br>
Subject: Re: [gpfsug-discuss] Independent fileset free inodes<br>
<br>
We have the same problem when we started using independent fileset. I<br>
think this should be a RFE item that IBM should provide a tool similar<br>
to 'mmdf -F' to show the number of free/used inodes for an independent<br>
fileset.<br>
<br>
Rei<br>
<br>
On 8/7/15 8:56 AM, Simon Thompson (Research Computing - IT Services) wrote:<br>
> I was just wondering if anyone had a way to return the number of free/used
inodes for an independent fileset and all its children.<br>
><br>
> We recently had a case where we were unable to create new files in
a child file-set, and it turns out the independent parent had run out of
inodes.<br>
><br>
> mmsf however only lists the inodes used directly in the parent fileset,
I.e. About 8 as that was the number of child filesets.<br>
><br>
> The suggestion from IBM support is that we use mmdf and then add up
the numbers from all the child filesets to workout how many are free/used
in the independent fileset.<br>
><br>
> Does anyone have a script to do this already?<br>
><br>
> Surely there is a better way?<br>
><br>
> Thanks<br>
><br>
> Simon<br>
> _______________________________________________<br>
> gpfsug-discuss mailing list<br>
> gpfsug-discuss at <a href="http://gpfsug.org">gpfsug.org</a><br>
> </font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size="2">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size="2"><br>
<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://gpfsug.org">gpfsug.org</a><br>
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size="2">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size="2"><br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://gpfsug.org">gpfsug.org</a><br>
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size="2">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size="2"><br>
<br>
</font></tt>
<br></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>gpfsug-discuss mailing list</span><br><span>gpfsug-discuss at <a href="http://gpfsug.org">gpfsug.org</a></span><br><span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></span><br></div></blockquote>
</div></body></html>
<br>
<div><img src="http://www.pixitmedia.com/sig/sig-cio.jpg"></div><div>This email is confidential in that it is intended for the exclusive attention of the addressee(s) indicated. If you are not the intended recipient, this email should not be read or disclosed to any other person. Please notify the sender immediately and delete this email from your computer system. Any opinions expressed are not necessarily those of the company from which this email was sent and, whilst to the best of our knowledge no viruses or defects exist, no responsibility can be accepted for any loss or damage arising from its receipt or subsequent use of this email.</div>