HPE Storage Users Group

Hello
I have 3par 8200 and issue with creating new snapshots
Manually or by schedule tasks .
Also the Expired snapshots can't be deleted

Error shown "volume Tree is being cleaned up try later"
After months error still exist

I tried many things but not succeeded
This post show all details

https://community.hpe.com/t5/hpe-3par-s ... 1Pzj4ixVkw

Can anyone help please

omarwaheed960 wrote:Hello
I have 3par 8200 and issue with creating new snapshots
Manually or by schedule tasks .
Also the Expired snapshots can't be deleted

Error shown "volume Tree is being cleaned up try later"
After months error still exist

I tried many things but not succeeded
This post show all details

https://community.hpe.com/t5/hpe-3par-s ... 1Pzj4ixVkw

Can anyone help please

Sounds like something is stuck. Have you tried logging a support case? Sounds you have a ticking bomb you need to address with one or multiple processes hung or stuck.

Hello
Could you provide the name of processes to check
Which system task to check ?
Any command that could resolve the issue
What about checkvv command

Keep in mind that issue of snapshot is the only issue on the storage system
So don't confuse with other issues in other storage in other posts

To my knowledge there are very few processes we can "touch" in the 3PAR OS. Most services will most likely require HPE to access the system with a root user. The only I can think of is system reporter, vasa, cim, wsapi and sysmgr.

The first four are unlikely to cause the issues you're seeing. The fifth one is dangerous. I'm on deep water here, but my understanding is that it is dependent of multiple sub-services. If one of those sub-services hang or is unable to restart then sysmgr might not be able to start. You may get into a situation where the 3PAR quickly becomes useless. I know at least that sysmgr or one of its sub-services is required for volumes to grow. So if sysmgr is down or not responding, the hosts will basically get a "disk full" message when they try to write when the thin volume is "full" and needs to grow in the system, which in best case might crash the server.

And again, without knowing what your actual issue is, I wouldn't be "trying and failing" to much with sysmgr. For all we know, it might not even be relevant or there could be an underlying issue that is causing your problems that could prevent sysmgr for restarting.


My first and probably only suggestion is to run checkhealth and see if that gives any pointers.

checkvv might be an alternative, but if you can't do volume management (create/delete snapshots) you most likely need to bring the volume offline to at least have any hopes of an impact.

Edit: you say that this is the only problem on "this" 3PAR ... Is this also only doing thin, or do you have dedupe/compression involved here?