quaint-alarm-7893
02/10/2023, 11:18 PMnarrow-egg-98197
02/11/2023, 2:34 PMdiskSelector
and nodeSelector
fields? ref. https://longhorn.io/docs/1.4.0/volumes-and-nodes/storage-tags/quaint-alarm-7893
02/11/2023, 5:38 PMallowVolumeExpansion: true
apiVersion: <http://storage.k8s.io/v1|storage.k8s.io/v1>
kind: StorageClass
metadata:
creationTimestamp: '2023-02-02T13:42:23Z'
name: hdd
resourceVersion: '180629798'
uid: f23599b7-49c6-407e-9cd8-184e0d03b27b
parameters:
diskSelector: hdd
migratable: 'true'
nodeSelector: lff
numberOfReplicas: '3'
staleReplicaTimeout: '30'
provisioner: <http://driver.longhorn.io|driver.longhorn.io>
reclaimPolicy: Delete
volumeBindingMode: Immediate
pics of rebuilding volume, node, and disk attached.narrow-egg-98197
02/12/2023, 2:14 PMEdit Node and Disks
option in Node tab
2. Delete the problem replica in Volume tab
3. Re-enable node: harvester-03quaint-alarm-7893
02/13/2023, 10:59 PMfailed to list snapshot: cannot get client for volume pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a: more than one engine exists
i just dont know how i can detach the PVC without deleting the data.
support bundle attachedhello everyone, i have a vm (in harvesteR) that got messed up when one of my servers had an issue, and now the VM is off, but the PVC is still attached. how can i detach it so i can bring the vm back online?
State: Attached
Health:
No node redundancy: all the healthy replicas are running on the same node Degraded
Ready for workload:Not Ready
Conditions:
restore
scheduled
Frontend:Block Device
Attached Node & Endpoint:
Size:
100 Gi
Actual Size:Unknown
Data Locality:disabled
Access Mode:ReadWriteMany
Backing Image:vdi-image-hzwdh
Backing Image Size:50 Gi
Engine Image:longhornio/longhorn-engine:v1.3.2
Created:a month ago
Encrypted:False
Node Tags:
Disk Tags:
Last Backup:
Last Backup At:
Replicas Auto Balance:ignored
Instance Manager:
instance-manager-e-c2f010c0
instance-manager-e-50d28d2d
Last time used by Pod:10 hours ago
Namespace:vdi
PVC Name:vmname-rootdisk-ossjw
PV Name:pvc-13787ebc-7d4e-41ad-9206-de9a6adb938a
PV Status:Bound
Revision Counter Disabled:False
Last Pod Name:virt-launcher-vmname-mpbn2
Last Workload Name:vmname
Last Workload Type:VirtualMachineInstance
note, it show's its attached to tow instance managers. i've tried rebooting the nodes, and deleting the instance manager pods, no luck...
sorry for the confusion. i have two issues, the disk-tag issue, and this volume not unmounting.
i can do the disk-tag issue next, if we can work this unmount issue out.