Duplicate directory appvolumes- <suffix with number> created on vSAN storage
Article ID: 337628
Updated On:
Products
VMware vSAN
Issue/Introduction
This is a corner case scenario and may occur outside App Volumes as well, e.g. during cluster rolling upgrade and reboot if someone creates the folder from the vCenter console, a collision may occur and "directory-<suffix>" created as well.
Symptoms:
During the package or writable creation/upload, if the “/appvolumes” folder is missing from the storage, App volumes Manager creates a new folder and subfolders like “/appvolumes/packages” and “/appvolumes/writable”.
In a corner case scenario, if a namespace object “/appvolumes” is unavailable due to network partition or cluster upgrade which involves the rebooting of all hosts. The new namespace object with the same name is created. When the network partition recovers, it will see two entries with the same name but different objects, it will resolve such name conflict by renaming one with a suffix. E.g "appvolumes" will be renamed to "appvolumes-1" (or "appvolumes-2" if "appvolumes-1" already exists and so on).
Symptoms:
During the package or writable creation/upload, if the “/appvolumes” folder is missing from the storage, App volumes Manager creates a new folder and subfolders like “/appvolumes/packages” and “/appvolumes/writable”.
In a corner case scenario, if a namespace object “/appvolumes” is unavailable due to network partition or cluster upgrade which involves the rebooting of all hosts. The new namespace object with the same name is created. When the network partition recovers, it will see two entries with the same name but different objects, it will resolve such name conflict by renaming one with a suffix. E.g "appvolumes" will be renamed to "appvolumes-1" (or "appvolumes-2" if "appvolumes-1" already exists and so on).
Environment
VMware App Volumes 4.x
VMware App Volumes 2.x
VMware App Volumes 2.x
Resolution
- If this scenario occurs, the admins should move the newly created packages and writables (if any) from the newly created directory eg.“appvolumes-1” to the correct directory “appvolumes” and delete the “appvolumes-1” from vSphere console using the file browser.
- Navigate to the App Volumes console and perform the import.
Additional Information
Impact/Risks:
If any packages are present on the newly created directory namespace “appvolumes-1”, then those packages might not be available for attachments as AVM will not have information about the new directory name.
If any packages are present on the newly created directory namespace “appvolumes-1”, then those packages might not be available for attachments as AVM will not have information about the new directory name.
Feedback
Yes
No
Powered by
