[gpfsug-discuss] Allocation map limits - any way around this?

[David D Johnson]

Whenever we start with adding disks of new sizes/speeds/controllers/machine rooms compared to existing NSD's in the filesystem, 
we generally add them to a new storage pool.  Add policy rules to make use of the new pools as desired, migrate stale
files to slow disk, active files to faster/newer disk, etc.  

> On Jul 10, 2018, at 8:29 AM, KG <spectrumscale at kiranghag.com> wrote:
> 
> Addendum to the question...
> 
> How is this calculated? I figured out it is based on NSD sizes that are initially used but not exactly how.
> 
> 
> ​KG​
> 
> On Tue, Jul 10, 2018 at 5:29 PM, Oesterlin, Robert <Robert.Oesterlin at nuance.com <mailto:Robert.Oesterlin at nuance.com>> wrote:
> File system was originally created with 1TB NSDs (4) and I want to move it to one 5TB NSD. Any way around this error?
> 
>  
> 
> mmadddisk fs1 -F new.nsd
> 
>  
> 
> The following disks of proserv will be formatted on node srv-gpfs06:
> 
>     stor1v5tb85: size 5242880 MB
> 
> Extending Allocation Map
> 
> Disk stor1v5tb85 cannot be added to storage pool Plevel1.
> 
> Allocation map cannot accommodate disks larger than 4194555 MB.
> 
> Checking Allocation Map for storage pool Plevel1
> 
> mmadddisk: tsadddisk failed.
> 
> Verifying file system configuration information ...
> 
> mmadddisk: Propagating the cluster configuration data to all
> 
>   affected nodes.  This is an asynchronous process.
> 
> mmadddisk: Command failed. Examine previous error messages to determine cause.
> 
>  
> 
>  
> 
> Bob Oesterlin
> 
> Sr Principal Storage Engineer, Nuance
> 
>  
> 
> 
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org <http://spectrumscale.org/>
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss <http://gpfsug.org/mailman/listinfo/gpfsug-discuss>
> 
> 
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180710/12d41351/attachment.htm>