Skip to content

Allow watchdog to clean up timed-out waiting mounts - #296

Merged
bharathsm-ms merged 1 commit into
release/3.0from
personal/bharathsm/CP-fix_stunnel_guardcheck
Feb 18, 2026
Merged

Allow watchdog to clean up timed-out waiting mounts#296
bharathsm-ms merged 1 commit into
release/3.0from
personal/bharathsm/CP-fix_stunnel_guardcheck

Conversation

@bharathsm-ms

Copy link
Copy Markdown
Collaborator

When a new NFSv4 mount is not progressing and its timeout (180s) has expired, the watchdog should clean up stunnel so that further mounts can succeed.

Previously, the NFS server refs guard in /proc/fs/nfsfs/servers blocked cleanup for all entries regardless of status, preventing recovery. Now the guard is only applied to mounted entries where k8s pods may still hold mount namespace refs. 'waiting' entries with expired timeouts bypass the guard so stunnel can be restarted.

Cherry pick from main branch: #295

When a new NFSv4 mount is not progressing and its timeout (180s) has
expired, the watchdog should clean up stunnel so that further
mounts can succeed.

Previously, the NFS server refs guard in /proc/fs/nfsfs/servers
blocked cleanup for all entries regardless of status, preventing
recovery. Now the guard is only applied to mounted entries where
k8s pods may still hold mount namespace refs. 'waiting' entries
with expired timeouts bypass the guard so stunnel can be restarted.

Signed-off-by: Bharath SM <bharathsm@microsoft.com>
@bharathsm-ms
bharathsm-ms merged commit a1a0091 into release/3.0 Feb 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants