Closed berendiwema closed 1 week ago
cifsd is NOT part of this driver, it's supplied by the host
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/close
I'm not sure if cifsd is a part of this driver, or is supplied by the host OS. I wasn't able to locate the cifsd process either on the file system of the affected hosts. Furthermore, reading the source code did not make it clear for me if cifds is a part of this driver or not.
I hope someone is familiair with issues like this and might know a way to mitigate it.
What happened: On several nodes within an OpenShift 4.13 cluster we see nodes with hanging CPUs due to cifsd driver issues.
What you expected to happen: The CIFSD driver does not cause hanging CPU's.
How to reproduce it: Difficult: looks like network issues cause the share to hang or a lock to timeout, but we haven't been able to pinpoint it.
Anything else we need to know?: System logs show:
Environment:
kubectl version
): Kubernetes Version: v1.26.13+8f85140uname -a
): 5.14.0-284.52.1.el9_2.x86_64