# Longhorn persistent volume not support for multi pod bind

**URL:** <https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728>\
**Category:** SUSE Storage\
**Created:** [September 11, 2018, 2:57pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728 "2018-09-11T14:57:04Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![bala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bala/32/4486_2.png) [@bala](https://forums.suse.com/u/bala)\
**Post date:** [September 11, 2018, 2:57pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/1 "2018-09-11T14:57:04Z")

</div>

Hi,

During deployment , using longhorn persistent volume with replica 2. but getting error while trying to mount pvc on pods. will Longhorn persistent volume support for multi pod bind with different worker nodes ?

Could please guide.

Thanks  
Bala

---

<div class="post-metadata">

**Author:** ![yasker](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/yasker/32/137_2.png) [@yasker](https://forums.suse.com/u/yasker)\
**Post date:** [September 11, 2018, 6:00pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/2 "2018-09-11T18:00:33Z")

</div>

Hi @bala

Longhorn is a Read-Write-Once type storage for Kubernetes. It’s the same as AWS EBS and Google Persistent Disk, which can only be mounted on one node. It’s a distributed block storage solution rather than a distributed file system solution, so it cannot be written at the same time for the different nodes.

You can use StatefulSet with VolumeClaimTemplate instead of Deployment. Kubernetes would create a PVC per Pod, so that’s one Longhorn volume per Pod. In this way, you can scale your workload easily with Longhorn.

---

<div class="post-metadata">

**Author:** ![bala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bala/32/4486_2.png) [@bala](https://forums.suse.com/u/bala)\
**Post date:** [September 11, 2018, 6:38pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/3 "2018-09-11T18:38:21Z")

</div>

Thank You much Yasker for explained.

Could please guide me the right persistent volume solution with Read write Many in Rancher Kubernetes

---

<div class="post-metadata">

**Author:** ![yasker](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/yasker/32/137_2.png) [@yasker](https://forums.suse.com/u/yasker)\
**Post date:** [September 11, 2018, 7:40pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/4 "2018-09-11T19:40:33Z")

</div>

You can take look at NFS.

---

<div class="post-metadata">

**Author:** ![bala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bala/32/4486_2.png) [@bala](https://forums.suse.com/u/bala)\
**Post date:** [September 12, 2018, 5:24am UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/5 "2018-09-12T05:24:48Z")

</div>

Any solution to implement block storage as pv ?

---

<div class="post-metadata">

**Author:** ![yasker](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/yasker/32/137_2.png) [@yasker](https://forums.suse.com/u/yasker)\
**Post date:** [September 12, 2018, 1:59pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/6 "2018-09-12T13:59:13Z")

</div>

Not sure what did you meant implement block storage a PV. Longhorn can be used as PV.

Though no block storage can support Read-Write-Many mode. It’s impossible since changing the storage content without filesystem knowing would result in data corruption.

---

<div class="post-metadata">

**Author:** ![bala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bala/32/4486_2.png) [@bala](https://forums.suse.com/u/bala)\
**Post date:** [September 12, 2018, 4:24pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/7 "2018-09-12T16:24:38Z")

</div>

Thanks Sheng Yang. Got it.

---

<div class="post-metadata">

**Author:** ![Gabriel\_P](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gabriel_p/32/6249_2.png) [@Gabriel\_P](https://forums.suse.com/u/Gabriel_P)\
**Post date:** [May 28, 2020, 11:36am UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/8 "2020-05-28T11:36:16Z")

</div>

Will this work with replica: 3 on a single pod?

---

<div class="post-metadata">

**Author:** ![yasker](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/yasker/32/137_2.png) [@yasker](https://forums.suse.com/u/yasker)\
**Post date:** [May 28, 2020, 2:32pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/9 "2020-05-28T14:32:27Z")

</div>

You can have 3 Longhorn replicas of a volume for a single pod.

---

<div class="post-metadata">

**Author:** ![Gabriel\_P](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gabriel_p/32/6249_2.png) [@Gabriel\_P](https://forums.suse.com/u/Gabriel_P)\
**Post date:** [May 29, 2020, 7:45am UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/10 "2020-05-29T07:45:15Z")

</div>

So if I have 2 replicas of the same Nodejs they don’t share a single storage volume?

---

<div class="post-metadata">

**Author:** ![robertorubioguardia](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/robertorubioguardia/32/3888_2.png) [@robertorubioguardia](https://forums.suse.com/u/robertorubioguardia)\
**Post date:** [September 23, 2021, 6:17pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/11 "2021-09-23T18:17:19Z")

</div>

Hi and sorry for replying on an old post.

“You can use StatefulSet with VolumeClaimTemplate instead of Deployment. Kubernetes would create a PVC per Pod, so that’s one Longhorn volume per Pod.”

Will the content of the 3 volumes be in sync?

New to all this Kubernetes experience.

Cheers,

---

<div class="post-metadata">

**Author:** ![shuo-wu](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/shuo-wu/32/6426_2.png) [@shuo-wu](https://forums.suse.com/u/shuo-wu)\
**Post date:** [October 7, 2021, 1:31pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/12 "2021-10-07T13:31:23Z")

</div>

For Longhorn each volume, there is no relationship with others **in Longhorn’s perspective**. But the workload, a StatefulSet using these volumes for example, would write the same content to them.

---

<div class="post-metadata">

**Author:** ![andreasnielsen87](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@andreasnielsen87](https://forums.suse.com/u/andreasnielsen87)\
**Post date:** [December 29, 2021, 12:36pm UTC](https://forums.suse.com/t/longhorn-persistent-volume-not-support-for-multi-pod-bind/11728/13 "2021-12-29T12:36:43Z")

</div>

> [@bala](#):
>
> solution to implement block storage as pv

You can create and access DigitalOcean Block Storage Volumes in a Kubernetes cluster by creating a PersistentVolumeClaim (PVC) as part of your deployment when you need to write and access persistent data. Using the Kubernetes command line tool, kubectl, this post will show you how to add volumes to your cluster.
