-
Notifications
You must be signed in to change notification settings - Fork 39.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubelet and btrfs snapshots: failed to check if disk space is available on the root partition: failed to get fs info for "root": error trying to get filesystem Device for dir /var/lib/kubelet #47046
Comments
@flavio There are no sig labels on this issue. Please add a sig label by: |
/sig storage |
kubernetes/kubernetes#47046 Signed-off-by: Flavio Castelli <fcastelli@suse.com>
kubernetes/kubernetes#47046 Signed-off-by: Flavio Castelli <fcastelli@suse.com>
kubernetes/kubernetes#47046 Signed-off-by: Flavio Castelli <fcastelli@suse.com>
I see the fix for btrfs is merged. Could we close this issue? |
Yes, the fix reached Kubernetes too because the vendored version of cadvisor has been upgraded. |
Kubernetes version (use
kubectl version
): 1.5.6 forwardEnvironment:
uname -a
): 4.4.62, but not really relevant in this caseWhat happened:
The system is using btrfs as main file system, several btrfs subvolumes are mounted under
/
, with/var/lib/kubelet
being one of them.cadvisor (and hence kubelet) can't determine the disk space available on the root partition because it gets confused by the subvolume major and minor IDs.
This is similar to #38337 but fix dc8b6cc is not enough for it.
I've already a fix for this issue, I'll follow up with a PR later today.
What you expected to happen:
No warnings from kubelet.
How to reproduce it (as minimally and precisely as possible):
/
/var/lib/kubelet
Anything else we need to know:
I've seen other similar issues, but none of them was about btrfs. The issues were about
tmpfs
orzfs
. My fix for this issue is going to be based on dc8b6cc hence it's going to be btrfs specific. That's why I filed this new issue.The text was updated successfully, but these errors were encountered: