* [PATCH] monitordisk: don't log when not monitoring a filesystem for inodes
@ 2014-09-25 14:31 Ross Burton
2014-09-25 16:05 ` Olof Johansson
0 siblings, 1 reply; 2+ messages in thread
From: Ross Burton @ 2014-09-25 14:31 UTC (permalink / raw)
To: bitbake-devel
Writing a log that the filesystem isn't being monitored for inode usage just
confuses users who are not aware about the nature of inodes in their filesystem,
so don't say anything, just silently disable the monitor. In general this only
happens on filesystems which don't have a limit on inodes.
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
bitbake/lib/bb/monitordisk.py | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/bitbake/lib/bb/monitordisk.py b/bitbake/lib/bb/monitordisk.py
index 6b03682..466523c 100644
--- a/bitbake/lib/bb/monitordisk.py
+++ b/bitbake/lib/bb/monitordisk.py
@@ -239,11 +239,9 @@ class diskMonitor:
freeInode = st.f_favail
if minInode and freeInode < minInode:
- # Some fs formats' (e.g., btrfs) statvfs.f_files (inodes) is
- # zero, this is a feature of the fs, we disable the inode
- # checking for such a fs.
+ # Some filesystems use dynamic inodes so can't run out
+ # (e.g. btrfs). This is reported by the inode count being 0.
if st.f_files == 0:
- logger.info("Inode check for %s is unavaliable, will remove it from disk monitor" % path)
self.devDict[k][2] = None
continue
# Always show warning, the self.checked would always be False if the action is WARN
--
1.7.10.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-09-25 16:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-09-25 14:31 [PATCH] monitordisk: don't log when not monitoring a filesystem for inodes Ross Burton
2014-09-25 16:05 ` Olof Johansson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.