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

KG spectrumscale at kiranghag.com
Tue Jul 10 13:29:59 BST 2018


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> 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://gpfsug.org/mailman/listinfo/gpfsug-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180710/af770acf/attachment-0002.htm>


More information about the gpfsug-discuss mailing list