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

[Jordan Robertson]

To second David's comments: I don't believe changing the max NSD size for a
given storage pool is possible (it may be tied to the per-pool allocation
mapping?), so if you want to add more dataOnly NSD's to a filesystem and
get that error you may need to create a new pool.

The tricky bit is that I think this only works with dataOnly NSD's, as
dataAndMetadata and metadataOnly NSD's only get added to the system pool
which is locked in like any other.

-Jordan

On Tue, Jul 10, 2018 at 10:28 AM, Uwe Falke <UWEFALKE at de.ibm.com> wrote:

> Hi Bob,
> you sure the first added NSD was 1 TB? As often as i created a FS, the max
> NSD size was way larger than the one I added initially , not just the
> fourfold.
>
> Mit freundlichen Grüßen / Kind regards
>
>
> Dr. Uwe Falke
>
> IT Specialist
> High Performance Computing Services / Integrated Technology Services /
> Data Center Services
> ------------------------------------------------------------
> ------------------------------------------------------------
> -------------------
> IBM Deutschland
> Rathausstr. 7
> 09111 Chemnitz
> Phone: +49 371 6978 2165
> Mobile: +49 175 575 2877
> E-Mail: uwefalke at de.ibm.com
> ------------------------------------------------------------
> ------------------------------------------------------------
> -------------------
> IBM Deutschland Business & Technology Services GmbH / Geschäftsführung:
> Thomas Wolter, Sven Schooß
> Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
> HRB 17122
>
>
>
>
> From:   "Oesterlin, Robert" <Robert.Oesterlin at nuance.com>
> To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
> Date:   10/07/2018 13:59
> Subject:        [gpfsug-discuss] Allocation map limits - any way around
> this?
> Sent by:        gpfsug-discuss-bounces at spectrumscale.org
>
>
>
> 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
>
>
>
>
>
> _______________________________________________
> 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/71378232/attachment.htm>