vSAN get rid of inaccessible object that is already deleted

[ahmad090]

hi,

after 2 disks failed in vsan i had some inaccessible VMs , once all issues were solved and all VMs are health now, i am still getting an inaccessible object (attached) this object id does not exist in vsan datastore, also in vSAN monitoring there is a trash button next to the inaccessible objects (attached) what does this button do and how to clear these errors.

regards,

[peetz]

Greetings,

here is a blog post that describes how to get rid of "unavailable" vSAN objects:

https://www.thinkcharles.net/blog/2018/2/16/removing-inaccessible-objects-in-vsan

I successfully followed these steps in at least two cases.

I would expect that the "trash" button in the GUI automates these steps, but I never tried it. In fact I haven't even noticed it so far. Must be new in 6.7 (U1).

Andreas

[ahmad090]

how can we make sure what this trash button do?

we have to make sure, using it may save us time than using RVC commands, if it does the same functionality

who can help us with this ?

[peetz]

I cannot find anything about this trash button in the official docs.

Maybe depping can chime in and help?

[TheBobkin · Accepted solution]

Hello ahmad090​,

Had a play with this in a lab, it doesn't delete Objects, it appears to merely clear the Objects selected for viewing placement details in the lower pane - I do think though that it could be named more clearly than 'thrash', it is also curiously clickable when invisible (though that could just be nested-HOL issues).

Exercise an extreme quantity of caution and care when deleting inaccessible Objects via RVC/objtool - unless you are 100% positive that you are not deleting something you may still need (e.g. unregistered VM Objects) then please do just contact GSS for assistance.

There are several ways of determining the identity of inaccessible Objects if it is not clear from the GUI/RVC but the simplest method in modern versions is just checking via 'esxcli vsan debug object list' (writing it to a file and then either less and find or grep for the lines after 'inaccessible' showing the path and then another grep to trim out the excess (e.g. 'cat /tmp/debuglist.txt | grep -A30 inaccessible | grep Path' - note that obviously that will only find these for standard layout FTM=RAID1 3-component Objects as the output structure of a larger Object would be more than 30 lines between where it shows the health status and the Path).

Bob