topic Re: MSA 2050 Overcommitted Storage Pool in MSA Storage

MSA 2050 Overcommitted Storage Pool

Tim Gowen — Mon, 30 Dec 2019 09:20:58 GMT

I have a problem with an MSA2050 which may be self-inflicted but I'm not sure how best to resolve it. This is the error:

I am new to MSA, so may have set it up incorrectly. The MSA is fully populated but the drives that have been created in Windows 2016 Server are not full.

How can I resolve this error?

The pool is set up like this:

Can I simply add a couple of large drives or remove some drives from the pool and restore the backup, or will the storage shrink with the data intact?

Re: MSA 2050 Overcommitted Storage Pool

SUBHAJIT KHANBARMAN_1 — Mon, 30 Dec 2019 11:20:55 GMT

Right now Pool A not yet full, just that page allocation reached to a state where it crossed high threshold and that's why Pool A show degraded

You can create new VDG with same 4 drives and same RAID10 then add it to Pool A. This should fix your issue.

I am not sure what is the condition of the Volume belongs to Pool A, I mean Thin provision size of the volume at MSA and how much space left in block level. Sameway how much space used at Windows filesystem level. If we consider space reclaim means if you delete data at the filesystem level then space reclaim at block level will be very slow because it happens in 4MB pages which will take huge time.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

************************************************************************

Re: MSA 2050 Overcommitted Storage Pool

Tim Gowen — Mon, 30 Dec 2019 11:49:02 GMT

Thanks, I have two volumes:

I'm guessing that it is 41% free in Windows.

The message about not shutting down or restarting is worrying me, especially as I need to update the firmware.

Re: MSA 2050 Overcommitted Storage Pool

SUBHAJIT KHANBARMAN_1 — Mon, 30 Dec 2019 14:11:30 GMT

As per the screenshot it clearly shows that Vol0001 allocated size 14.2TB but you said 41% free at the Windows Filesystem level for the same volume which means lots of space remaining reclaim back at the block level. Not sure how you get into this situation but ideally you must have deleted data from filesystem level over a period of time or suddenly deleted big amount of data which created this situation. That's why windows fielsystem level even though you have free space but block level you need to create that free space means windows filesystem and block level need to sync up so that same amount of space will get occupied.

Quick solution would be to take data backup, delete Vol0001 and recreate the Vol0001 again. Then restore data from backup.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************

Re: MSA 2050 Overcommitted Storage Pool

Cali — Tue, 07 Jan 2020 16:03:01 GMT

On Windows Side check if Space Relaim is set on: fsutil behavior set DisableDeleteNotify 0

Google for: sdelete windows space reclaim

Check for:

defrag x: /L
PS C:\> Optimize-Volume -DriveLetter X -ReTrim –Verbose

Cali