I would as I suggested add the new NSD into a new pool in the same filesystem. Then I would migrate all the files off the old pool onto the new one. At this point you can deldisk the old ones or decide what else you’d want to do with them.
-- ddj Dave Johnson > On Jul 10, 2018, at 12:29 PM, Oesterlin, Robert <[email protected]> > wrote: > > Right - but it doesn’t give me the answer on how to best get around it. :-) > > > Bob Oesterlin > Sr Principal Storage Engineer, Nuance > > > > From: <[email protected]> on behalf of IBM Spectrum > Scale <[email protected]> > Reply-To: gpfsug main discussion list <[email protected]> > Date: Tuesday, July 10, 2018 at 11:18 AM > To: gpfsug main discussion list <[email protected]> > Subject: [EXTERNAL] Re: [gpfsug-discuss] Allocation map limits - any way > around this? > > The only additional piece of information I would add is that you can see what > the maximum NSD size is defined for a pool by looking at the output of mmdf. > > Fred > _______________________________________________ > 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
