summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2014-09-25 15:28:52 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-09-29 12:04:28 +0100
commitca93bc84ee5fb94a50c11c47e4d212d7da649e24 (patch)
treeab20661321a28ee7c0c6571bb785047ac6797ccf
parent637ce8df2658e4905fab8a0600a45505596bf472 (diff)
downloadbitbake-ca93bc84ee5fb94a50c11c47e4d212d7da649e24.tar.gz
monitordisk: don't log when not monitoring a filesystem for inodes
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> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--lib/bb/monitordisk.py6
1 files changed, 2 insertions, 4 deletions
diff --git a/lib/bb/monitordisk.py b/lib/bb/monitordisk.py
index 6b0368258..466523c6e 100644
--- a/lib/bb/monitordisk.py
+++ b/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