Remount when connection lost

[barthofu]

Is your feature request related to a problem?/Why is this needed

Hello, i don't really know if it's an intended or normal behavior but each time i'm losing my NFS connection and then get it back up, it won't remount the disks in my pods.

I'm then in the obligation of restarting the pods...

Would it be possible to automate the NFS remount into the pod?

[andyzhangx]

@barthofu have you tried -o hard mount option?

there is an NFS mount option that you can use to remount the NFS share when the server is unavailable and then recovers. The option is called hard and it makes the NFS client keep retrying the NFS server indefinitely until it becomes available again.

Here's an example command to mount an NFS share with the hard option:

mount -t nfs -o hard <nfs-server>:<nfs-share> <mount-point>

[bogdanpetrea]

I think unless you specify soft, hard is on by default.

Edit: In a much older issue from the kubernetes repo (which I assume is a different implementantion from the csi-driver one), someone mentioned they fixed their problem by using a different NFS server image: kubernetes/kubernetes#75918 (comment)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten