topic The virtual pool space limit has been reached. The pool is full in MSA Storage

The virtual pool space limit has been reached. The pool is full

kavandi — Thu, 05 Jan 2023 08:59:23 GMT

Hi Dear

I have received the following error today at MSA Storage 2062

"Acknowledgement Details: Alert acknowledged by manage on 2023-01-04 08:14:45

Description: The virtual pool space limit has been reached. The pool is full.

Recommended Action: - Add a disk group, or remove data from the pool to reduce the space usage below the high threshold. Do not shut down or remove the controller modules until space usage is below the high threshold."

DiskGroup has a volume that mapped to a hp dl380 g9 in the form of a datastore with 8TB capacity.

datastore has serveral VM and 1TB free space. now all VM stopped with this error

"There is no more space for virtual disk 'sample.vmdk'. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session.

Retry

Cancel"

Please help me

I can't delete volume or diskgroup. and there isn't any space for adding hard disk for expanding or creating another diskgroup.

I don't know why it happened

thank you for your helping

Re: The virtual pool space limit has been reached. The pool is full

JonPaul — Wed, 04 Jan 2023 18:38:39 GMT

@kavandi
We will need more details on the configuration of the MSA.
Pools, Disk-Groups, Volumes
The MSA virtual Storage allows Thin-Provisioning which will allow you to display/provision to your hosts more capacity than is available. While the OS will report an 8TB volume and only 7TB in use, this is only the information at the host level and does not necessarily represent what is used on the array. There could be other volumes or Snapshots which are using space within the pool.

Re: The virtual pool space limit has been reached. The pool is full

kavandi — Mon, 09 Jan 2023 06:25:10 GMT

@JonPaul

Thank you for Reply

you are right. I had Replication between 2 storage devices and after deleted snapshots and Replication rule, my problem was resolved

How can I increase space for snapshots? should I delete my volumes and create them again with part of diskgroup capacity?

how much disk gruop space should be free for replication and save 2 snapshots?

thank you

Re: The virtual pool space limit has been reached. The pool is full

JonPaul — Tue, 10 Jan 2023 21:28:40 GMT

@kavandi
With both Snapshots and Replications you can set parameters of when to auto delete them to free capacity. The snapshots will use available space on the Pool. As you experienced it used all space that was not used by the original volumes. At this point if you want more space for snapshots you will need to expand the Pool.
Snapshots are a point in time 'copy' of the original data. An initial snapshot will take very little storage capacity as it is just a set of pointers back to the original volume data but as the original volume data changes the 'old' data will fill the snapshot and expand the total capacity needed to retain both the Volume data and Snapshot data. To determine how much space you need for snapshots is based upon how much data change you have. If you have 100% data change then the each snapshot could be the same size as the original data. More likely rate of change is much smaller, the default Snapshot Space is 10% and can be adjusted: See MSA 2060 CLI Guide: https://www.hpe.com/psnow/doc/a00105313en_us set snapshot-space

Re: The virtual pool space limit has been reached. The pool is full

kavandi — Tue, 17 Jan 2023 09:26:16 GMT

thanks

Re: The virtual pool space limit has been reached. The pool is full

Sunitha_Mod — Thu, 19 Jan 2023 07:54:29 GMT

Hello @kavandi,

We are glad to know the problem has been resolved.