# Multi-Attach error for volume "pvc "Volume is already exclusively attached to one node and can't be attached to another" **URL:** \ **Category:** General Discussions\ **Created:** [February 1, 2022, 5:59pm UTC](https://discuss.kubernetes.io/t/multi-attach-error-for-volume-pvc-volume-is-already-exclusively-attached-to-one-node-and-cant-be-attached-to-another/18951 "2022-02-01T17:59:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Ruben\_Goncalves](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/ruben_goncalves/32/9448_2.png) [@Ruben\_Goncalves](https://discuss.kubernetes.io/u/Ruben_Goncalves)\ **Post date:** [February 1, 2022, 5:59pm UTC](https://discuss.kubernetes.io/t/multi-attach-error-for-volume-pvc-volume-is-already-exclusively-attached-to-one-node-and-cant-be-attached-to-another/18951/1 "2022-02-01T17:59:57Z")
Kubernetes version1.22.2 Cloud Provider Vsphere version 6.7 Architecture: 3 Masters 15 Workers What happened: One of the pods for some “unknown” reason went down, and when we try to lift him up, it couldn’t attach the existing PVC. This only happened to a specific pod, all the others didn’t have any kind of problem. What did you expect to happen: Pods should dynamically assume PVCs Validation: First step: The connection to Vsphere has been validated, and we have confirmed that the PVC exists. Second step: The Pod was restarted (Statefulset 1/1 replicas) to see if the pod would rise again and assume the pvc, but without success. Third step: Made a restart to the services (kube-controller, kube-apiserve, etc) Last step: All workers and masters were rebooted but without success, each time the pod was launched it had the same error Multi-Attach error for volume pvc.Volume is already exclusively attached to one node and can’t be attached to another"" When I delete a pod and try to recreate it, I get this warning: Multi-Attach error for volume “pvc…” The volume is already exclusively attached to a node and cannot be attached to another Anything else we need to know: I have a cluster (3 master and 15 nodes) Temporary resolution: Erase the existing PVC and launch the pod again to recreate the PVC. Since this is data, it is not the best solution to delete the existing PVC. Multi-Attach error for volume “pvc-…” Volume is already exclusively attached to one node and can’t be attached to another ---
**Author:** ![lin.xiaofeng](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/lin.xiaofeng/32/9798_2.png) [@lin.xiaofeng](https://discuss.kubernetes.io/u/lin.xiaofeng)\ **Post date:** [April 3, 2022, 4:24pm UTC](https://discuss.kubernetes.io/t/multi-attach-error-for-volume-pvc-volume-is-already-exclusively-attached-to-one-node-and-cant-be-attached-to-another/18951/2 "2022-04-03T16:24:48Z")
I have the same problem. When I shut down a host, the running POD on it will be rebuilt, but the PV will not be mounted at first, and it will be restored after 6 minutes. How can I skip the 6 minute wait time? k8s: v1.22.7-k3s1 Longhorn: v1.2.4 ![pvc-error](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/e/e3719830cfe4cba873219f82f250ce9120ccc796.png) ---
**Author:** ![nileshkirve](https://avatars.discourse-cdn.com/v4/letter/n/977dab/32.png) [@nileshkirve](https://discuss.kubernetes.io/u/nileshkirve)\ **Post date:** [November 16, 2022, 6:11am UTC](https://discuss.kubernetes.io/t/multi-attach-error-for-volume-pvc-volume-is-already-exclusively-attached-to-one-node-and-cant-be-attached-to-another/18951/3 "2022-11-16T06:11:28Z")
Just simply, scale down your deployment and then scale up Scale down: [local@jump Nilesh]$ oc -n scale deployment --replicas=0 Scale up: [local@jump Nilesh]$ oc -n scale deployment --replicas=1 Pods status mysql-57 1/1 Running 8m38s ---
**Author:** ![pchan](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@pchan](https://discuss.kubernetes.io/u/pchan)\ **Post date:** [November 16, 2022, 9:49am UTC](https://discuss.kubernetes.io/t/multi-attach-error-for-volume-pvc-volume-is-already-exclusively-attached-to-one-node-and-cant-be-attached-to-another/18951/4 "2022-11-16T09:49:26Z")
Did the “unknown reason” by any chance happen to be a node shutdown ? There is a fix in K8s 1.25 which fixes the non-graceful node shutdown ([link](https://kubernetes.io/blog/2022/05/20/kubernetes-1-24-non-graceful-node-shutdown-alpha/)).