MSA2060 SAS on Windows and message "A virtual pool exceeded its high page threshold "

[IMPI-Ced]

Hi,

Lets first see the setup 

• Proliant under windows 2022
• MSA 2060 with 20x 3.8TB SSD, only pool A, mounted on windows using SAS, reFS formatted
• Used for Veeam backup
• All is working fine

i have a weird thing : a message telling me that i'm overprovisionned, but if i look deaper i'm told that overprovisonned is 0.0 KB ! (see pictures bellow)

Then i do not understand where is the problem, also, on windows, i have 20 TB free on the 60 total, then it should be ok

On this forum i found things about ESX and unmap command, but here what can i do ?

I think i misunderstand something...

Thanks for your help

Ced

[Moderator edit: Erased the confidential info.]

[IMPI-Ced]

Hi all,

i keep on searching and found some things on veeam forum that space is not reclaimed, not sure it has to deal with my issue.

What i did :

> fsutil behavior query disableDeleteNotify
NTFS DisableDeleteNotify = 0 (Autorise l’envoi d'opérations TRIM au dispositif de stockage)
ReFS DisableDeleteNotify = 0 (Autorise l’envoi d'opérations TRIM au dispositif de stockage)

this was already done some times ago

Then :

> Optimize-Volume -driveletter e -ReTrim -Verbose

it tells me it optimize 14 TB, but nothing changes on MSA

Also did a > defrag e: /L /V

same result as above,

I'm now trying >sdelete64.exe -z e: that is said to work better

It seems that the MSA did not see freeed blocks

Any help is appreciated !

Thanks

Ced

[Cali]

Hi,

if you have only one big Volume for Backup, I usually disable Overprovisioning to prevent this.
It's safer.

set pool overcommit off A

Cali

[IMPI-Ced]

Hi Cali

thanks for this reply.

Yes, there's only one big volume, taking 100% of the MSA

Is it safe to do "set pool overcommit off A"  ? Because in GUI, i found an option to disable it but i can not and it say it is because i overcommit (i do not agree with that because as you can see on the picture it say 0 to overcommit)

A scrub is running, will it help doing some "space reclaim" ?

Thanks for your help

[Cali]

Yes, because the volume is currently larger than it physically exists, which is your problem.
You would have to delete it and create it again without overcommitting, then it can only be as large as it is physically.

Cali

[IMPI-Ced]

Cali, sorry if i misunderstand but my volume is not larger than the physical space : physical is 61.4TB,  and i'm using 61.1

You can see it on previous pictures and on both bellow

Also, when i last expanded it, i said  "use all capacity" then i did not say "use more capacity than i have"

I do not have ressources to copy all (30 TB) of that elsewhere, delete the volume, recreate and take back... And as this is in fact refs, i'll loose deduplication and then in fact i'll have to deal with more than 100Tb of data... then unable to put back then

Many thanks for your help !

Ced

[Cali]

Now back to your Case, from the Manual:

Middle Threshold. When this percentage of virtual pool capacity has been used, the system will generate an alert and event
462 to notify the administrator to add capacity to the pool. This value must be between the Low Threshold and High
Threshold values. The default is 75%. If the pool is not overcommitted, the alert will have informational severity. If the
pool is overcommitted, the alert will have Warning severity.

High Threshold
When this percentage of virtual pool capacity has been used, the system will generate an alert and event
462 to alert the administrator to add capacity to the pool. This value is automatically calculated as the available capacity of
the pool minus 400GiB — or if that result is below the mid threshold, then mid threshold capacity plus 1%. If the pool is not
overcommitted, the alert will have Informational severity. If the pool is overcommitted, the alert will have Warning
severity and the system will use write-through cache mode until virtual pool usage drops back below this threshold.

So the Warning in your Case is intended and in order I would say.

Cali

[IMPI-Ced]

OK, thanks for clarification.

Then i'm not overcommited, but as there is less than 400 GB remaining i'm considered as overcommitted.

Should i try to type the command you gave me (set pool overcommit off A) ?

Sure there is the solution to add one disk (3.8 TB SSD are quite expensive).

Is that dangerous to remain like that ?

Ced

[ngnear]

It shouldn't cause any data loss however you might face IOPs issue.

It's better to have a support case logged for further in depth analysis for this and share the SMU logs once for diagnosis.

You can log a support case at https://support.hpe.com/

[IMPI-Ced]

thanks ngnear for this reply.

 Not sure i have the right to log a support case for this hardware, i'll have a look

By the way i'll keep updated

Ced

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[IMPI-Ced]

Hi,

sorry for giving no news, i did not take time to go further.

I'm still surprised that having extented my volume using "use max space" i'm now facing this issue where i still have space (260 Go) but i'm told that i'm overcommited.... and overcommitment is ay 0

I'll try to take time to go further

Ced