Derek Su

> > To prevent from the mistaken deletion of the engineimage, we can count the number of replicas and engines using the image rather than the number of volumes. >...

After investigating the logs of the three problematic volumes, the three volumes all only have one replica and the volume.meta's rebuilding field are set to `true`. Because the information in...

> @derekbit @PhanLe1010 I’m not sure how to reproduce this issue and what’s the test steps to verify this issue. Could you give some hints? Thank you! @yangchiu Update the...

> 4\. workload and the volume is attached: the problematic replica marked error then delete, a new replica rebuilt, all replicas back to running. The volume will be not stuck...

@amadub Did you try this https://longhorn.io/docs/1.2.3/high-availability/node-failure/#longhorn-pod-deletion-policy-when-node-is-down? This issue is related to `Pod Deletion Policy When Node is Down` and you can set it to `delete-both-statefulset-and-deployment-pod`.

> Also note, This issue does not exist if I have replication turned on in longhorn, but that is not an ideal fix for my current application. @amadub So, you...

For the volume with single replica, if the replica is on the down node, Longhorn cannot restart the volume on another node automatically. Manual intervention is necessary in this case....

**OS: ubuntu 20.04 (kernel: 5.4.0)** **K8s: v1.23.6+k3s1** **Investigate two behaviors** **1. node, which has the volume and the share-manager pod, is not crashed or shut down, but the share-manager pod...

**OS: ubuntu 22.04 (kernel: 5.15.0)** **K8s: v1.23.6+k3s1** The incomplete IO operation is retried in the second case in the above comment after the volume and share-manager pod are re-created on...

The `Lease_Lifetime` of the NFS server is 60 seconds. The value should be decreased but also need to investigate if there is any downside. https://www.suse.com/support/kb/doc/?id=000019374 https://github.com/longhorn/longhorn-share-manager/blob/5b57b596e192d758f3049142a7ced47c0b0dae03/pkg/server/nfs/nfs_server.go#L37