VMware Cloud Community
SelimAtmaca
Contributor
Contributor
Jump to solution

Unassociated objects on VSAN

Vsphere6.5

Horizon7.4.0

If I run the command below on RVC, it shows many unassociated objects on VSAN (screenshot attached to the post).

vsan.obj_status_report computers/VDI_CLUSTER/ -t

I am planning to delete them  by using the escxcli command below. Is it safe to delete those un-associated objects like this? I would like to keep VSAN clean, what would you recommend? Is there a easy-way to delete those objects or do I have to enter the command  for each folder one by one? I have never used scripting on Vmware, please advise.

/usr/lib/vmware/osfs/bin/osfs-rmdir <foldername> -f

1 Solution

Accepted Solutions
TheBobkin
Champion
Champion
Jump to solution

Hello SelimAtmaca​,

The first thing to do is to identify the Objects - you need to be exceedingly careful with this as there are a LOT of ways that in-use Object may be classified as Unassociated Object, some of the main types/reasons for this are noted in the kb Alessandro linked (which it would happen is an article I wrote :smileygrin: ).

Unassociated does NOT mean Inaccessible.

I do not like the 3rd article linked above as it makes no effort at identifying what the Objects are - just because an Object is Inaccessible doesn't mean it is going to stay this way and you could be deleting the only current copy (which is Inaccessible due to loss of quorum as opposed to being stale).

"/usr/lib/vmware/osfs/bin/osfs-rmdir <foldername> -f"

This is neither an esxcli command nor the correct command for deleting Objects - that would be objtool.

If you have a support contract with VMware I would strongly advise opening a Support Request with us to take a better look here.

Bob

View solution in original post

3 Replies
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

Yes you can, you just have to be very careful what you erase.

Here are some links that can be useful:

ARomeo

Blog: https://www.aleadmin.it/
TheBobkin
Champion
Champion
Jump to solution

Hello SelimAtmaca​,

The first thing to do is to identify the Objects - you need to be exceedingly careful with this as there are a LOT of ways that in-use Object may be classified as Unassociated Object, some of the main types/reasons for this are noted in the kb Alessandro linked (which it would happen is an article I wrote :smileygrin: ).

Unassociated does NOT mean Inaccessible.

I do not like the 3rd article linked above as it makes no effort at identifying what the Objects are - just because an Object is Inaccessible doesn't mean it is going to stay this way and you could be deleting the only current copy (which is Inaccessible due to loss of quorum as opposed to being stale).

"/usr/lib/vmware/osfs/bin/osfs-rmdir <foldername> -f"

This is neither an esxcli command nor the correct command for deleting Objects - that would be objtool.

If you have a support contract with VMware I would strongly advise opening a Support Request with us to take a better look here.

Bob

SelimAtmaca
Contributor
Contributor
Jump to solution

Thanks a lot

Reply
0 Kudos