From ff642ff0cf428bd0d833e7eafd06c69e7217d931 Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Thu, 25 Sep 2014 15:28:52 +0100 Subject: [PATCH] bitbake: 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. (Bitbake rev: ca93bc84ee5fb94a50c11c47e4d212d7da649e24) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie --- 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 -- 2.7.4