we have GPFS126.96.36.199 and following error
mmadddisk tsmt05_db -F crnsd_vsp_db.txt
GPFS: 6027-531 The following disks of tsmt05_db will be formatted on node r3p8l05a1.lan.huk-coburg.de:
DSK3D_db_1: size 562883584 KB
DSK7D_db_1: size 562883584 KB
Extending Allocation Map
GPFS: 6027-594 Disk DSK3D_db_1 cannot be added to storage pool 'system'.
Allocation map cannot accommodate disks larger than 265009 MB.
Checking Allocation Map for storage pool 'system'
mmadddisk: 6027-1204 tsadddisk failed.
Verifying file system configuration information ...
mmadddisk: 6027-1371 Propagating the cluster configuration data to all
affected nodes. This is an asynchronous process.
mmadddisk: 6027-1639 Command failed. Examine previous error messages to determine cause.
We searched in the Forum and found that the problem is the initial allocation map. Can everone explain the Problem here. Why we see here the restriction to swap a nsd group with a new one. Our plan was to add new nsd's with more capacity (old one was 25 GB and new one 565 GB), delete the old one's. The hints with a new pool was only for data and what is with the metadata disk there? Are there any other solutions for that?
Any hints are great. Thanks Renar
kalcig 270002R7E826 Posts
Re: Extending Allocation Map - Issue2012-11-23T05:16:46ZThis is the accepted answer. This is the accepted answer.The maximum disk size that can be added to the filesystem is decided at fs creation time based on number of disks used to create fs and its size. And a msg of the largest disk size allowed is printed during mmcrfs.
This has been discussed already here:
renarg 100000G60J127 Posts
Re: Extending Allocation Map - Issue2012-11-23T13:26:21ZThis is the accepted answer. This is the accepted answer.
- kalcig 270002R7E8
thanks for this hint. Are there any formula for that behavior, on wich size and count of disk, we can use for planing purpose.