Here is the yaml file for reference

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: longhorn-volv-pvc-2
  namespace: default
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn
  resources:
    requests:
      storage: 50Gi
---
apiVersion: v1
kind: Pod
metadata:
  name: volume-test-2
  namespace: default
spec:
  restartPolicy: Always
  containers:
  - name: volume-test
    image: nginx:stable-alpine
    imagePullPolicy: IfNotPresent
    livenessProbe:
      exec:
        command:
          - ls
          - /data/lost+found
      initialDelaySeconds: 5
      periodSeconds: 5
    volumeMounts:
    - name: volv
      mountPath: /data
    ports:
    - containerPort: 80
  volumes:
  - name: volv
    persistentVolumeClaim:
      claimName: longhorn-volv-pvc-2
---
apiVersion: v1
kind: Pod
metadata:
  name: volume-test-3
  namespace: default
spec:
  restartPolicy: Always
  containers:
  - name: volume-test
    image: nginx:stable-alpine
    imagePullPolicy: IfNotPresent
    livenessProbe:
      exec:
        command:
          - ls
          - /data/lost+found
      initialDelaySeconds: 5
      periodSeconds: 5
    volumeMounts:
    - name: volv
      mountPath: /data
    ports:
    - containerPort: 80
  volumes:
  - name: volv
    persistentVolumeClaim:
      claimName: longhorn-volv-pvc-2

Ah, here's the issue that I found. If I move the second pod to another node, I get this error: Normal Scheduled 37s default-scheduler Successfully assigned default/volume-test-3 to node-2 Warning FailedAttachVolume 38s attachdetach-controller Multi-Attach error for volume "pvc-17688251-ae9e-41d2-817c-70564f2cc9db" Volume is already used by pod(s) volume-test-2 My understanding is Longhorn will not allow multi writes from different nodes.