[gpfsug-discuss] undo fileset inode allocation

Eric Horst erich at uw.edu
Fri Jan 6 19:07:22 GMT 2017


Greetings all,

I've been setting up and migrating to a new 225TB filesystem on 4.2.1.
Separate data and metadata disks. There are about 20 independent filesets
as second level directories which have all the files. One of the
independent filesets hit its inode limit of 28M. Without carefully checking
my work I accidentally changed the limit to 3.2B inodes instead of 32M
inodes. This ran for 15 minutes and when it was done I see mmdf shows that
I had 0% metadata space free. There was previously 72% free.

Thinking about it I reasoned that as independent filesets I might get that
metadata space back if I unlinked and deleted that fileset. After doing so
I find I have metadata 11% free. A far cry from the 72% I used to have. Are
there other options for undoing this mistake? Or should I not worry that
I'm at 11% and assume that whatever was preallocated will be productively
used over the life of this filesystem?

Thanks,

-Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170106/7a4ce24d/attachment-0001.htm>


More information about the gpfsug-discuss mailing list