<font size=2 face="sans-serif">Question and Suggestion: Do you have
any snapshots that might include files that were in the fileset you are
attempting to delete? Deleting those snapshots will allow the fileset
deletion to complete. The snapshots are kinda intertwined with what
was the "live" copy of the inodes. In the GPFS "ditto"
implementation of snapshotting, for a file that has not changed since
the snapshot operation, the snapshot copy is not really a copy but just
a pointer to the "live" file. So even after you have logically
deleted the "live" files, the snapshot still points to those
inodes you thought you deleted. Rather than invalidate the snapshot,
(you wouldn't want that, would you?!) GPFS holds onto the inodes, until
they are no longer referenced by any snapshot.<br></font><br><font size=2 face="sans-serif">--marc </font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Luke Raimbach <Luke.Raimbach@crick.ac.uk></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug main discussion
list <gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">07/01/2016 06:32 AM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[gpfsug-discuss]
Trapped Inodes</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><tt><font size=2>Hi All,<br><br>I've run out of inodes on a relatively small filesystem. The total metadata
capacity allows for a maximum of 188,743,680 inodes.<br><br>A fileset containing 158,000,000 inodes was force deleted and has gone
into a bad state, where it is reported as (NULL) and has state "deleted":<br><br>Attributes for fileset (NULL):<br>===============================<br>Status
Deleted<br>Path
--<br>Id
15<br>Root inode
latest:<br>Parent Id
<none><br>Created
Wed Jun 15 14:07:51 2016<br>Comment<br>Inode space
8<br>Maximum number of inodes
158000000<br>Allocated inodes
158000000<br>Permission change flag
chmodAndSetacl<br>afm-associated
No<br><br>Offline mmfsck fixed a few problems, but didn't free these poor, trapped
inodes. Now I've run out and mmdf is telling me crazy things like this:<br><br>Inode Information<br>-----------------<br>Total number of used inodes in all Inode spaces:
0<br>Total number of free inodes in all Inode spaces:
27895680<br>Total number of allocated inodes in all Inode spaces: 27895680<br>Total of Maximum number of inodes in all Inode spaces: 34100000<br><br><br>Current GPFS build: "4.2.0.3".<br><br>Who will help me rescue these inodes?<br><br>Cheers,<br>Luke.<br><br>Luke Raimbach​<br>Senior HPC Data and Storage Systems Engineer,<br>The Francis Crick Institute,<br>Gibbs Building,<br>215 Euston Road,<br>London NW1 2BE.<br><br>E: luke.raimbach@crick.ac.uk<br>W: </font></tt><a href=www.crick.ac.uk><tt><font size=2>www.crick.ac.uk</font></tt></a><tt><font size=2><br><br>The Francis Crick Institute Limited is a registered charity in England
and Wales no. 1140062 and a company registered in England and Wales no.
06885462, with its registered office at 215 Euston Road, London NW1 2BE.<br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<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></font></tt><br><BR>