A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/vmware/docker-volume-vsphere/issues/1649 below:

If vm is reverted to a snapshot while container is running, volume remains in attached state after revert finishes. · Issue #1649 · vmware-archive/vsphere-storage-for-docker · GitHub

This repository was archived by the owner on Nov 9, 2020. It is now read-only.

This repository was archived by the owner on Nov 9, 2020. It is now read-only.

If vm is reverted to a snapshot while container is running, volume remains in attached state after revert finishes. #1649

Description
  1. Took two snapshots.
  2. Ran a container with volume mounted.
  3. With container running, reverted to latest snaphot.
  4. After revert finishes, volume remains attached, hence volume removal also fails and we have a left-over volume.

Logs have been attached at the end.

Volume name: VolSS1

root@sc-rdops-vm02-dhcp-52-237:~# docker volume inspect VolSS1
[
    {
        "Driver": "vsphere:latest",
        "Labels": {},
        "Mountpoint": "/mnt/vmdk/VolSS1",
        "Name": "VolSS1",
        "Options": {},
        "Scope": "global",
        "Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "attached to VM": "ubuntu-VM0.1",
            "attachedVMDevice": {
                "ControllerPciSlotNumber": "160",
                "Unit": "0"
            },
            "capacity": {
                "allocated": "15MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Thu Jul 27 18:27:38 2017",
            "created by VM": "ubuntu-VM0.1",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "attached"
        }
    }
]
root@sc-rdops-vm02-dhcp-52-237:~#
root@sc-rdops-vm02-dhcp-52-237:~#
root@sc-rdops-vm02-dhcp-52-237:~# docker volume rm VolSS1
Error response from daemon: unable to remove volume: remove VolSS1: VolumeDriver.Remove: Failed to remove volume VolSS1, in use by VM = ubuntu-VM0.1.
root@sc-rdops-vm02-dhcp-52-237:~#

[root@sc-rdops-vm07-dhcp-192-56:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py volume ls
Volume     Datastore     VMGroup   Capacity  Used  Filesystem  Policy  Disk Format  Attached-to   Access      Attach-as               Created By    Created Date
---------  ------------  --------  --------  ----  ----------  ------  -----------  ------------  ----------  ----------------------  ------------  ------------------------
TestVolSS  sharedVmfs-0  _DEFAULT  100MB     15MB  ext4        N/A     thin         ubuntu-VM0.1  read-write  independent_persistent  ubuntu-VM0.1  Thu Jul 27 18:07:03 2017
VolSS1     sharedVmfs-0  _DEFAULT  100MB     15MB  ext4        N/A     thin         ubuntu-VM0.1  read-write  independent_persistent  ubuntu-VM0.1  Thu Jul 27 18:27:38 2017

Logs:
docker-volume-vsphere.txt
vmdk_ops.txt


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4