Red Hat Bugzilla – Bug 1511576
fs.go:359] Stat fs failed. Error: no such file or directory
Last modified: 2018-03-28 10:12:38 EDT
I see a bunch of these messages, but they don't tell me what to do. Do they matter? Is there something to fix? fs.go:359] Stat fs failed. Error: no such file or directory # rpm -q atomic-openshift-node atomic-openshift-node-3.6.173.0.5-1.git.0.f30b99e.el7.x86_64 # journalctl --since=-30m | grep 'Stat fs failed.' | wc -l 1573
Comes from here https://github.com/google/cadvisor/blob/master/fs/fs.go#L418 Basically the syscall.Statfs() call that getVfsStats() calls returns this error. Probably in response to a failed/terminated container. Do you see this recurring over and over for the same path? Or just one or two times per path? If just one or two times, then this is log spam and should likely be reduced from Error to V(3).
Someone will need to dig a bit. For example on starter-us-east-1-node-compute-d9c25 I see that message 1500 times in 30 minutes. And I have no idea what the path is. It isn't in the log...
*** Bug 1512714 has been marked as a duplicate of this bug. ***
Seems like this was fixed with https://github.com/kubernetes/kubernetes/pull/17883
Tomas, which commit in cadvisor fixed this?
Upstream cadvisor: https://github.com/google/cadvisor/pull/1847 Origin PR: https://github.com/openshift/origin/pull/18181
Checked with v3.9.0-0.22.0, and this issue has been fixed. # journalctl --since=-30m | grep 'Stat fs failed.' | wc -l 0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489