linux/poky.git/bitbake/lib/bb/monitordisk.py, branch dizzy-12.0.1

bitbake: monitordisk: don't log when not monitoring a filesystem for inodes

2014-09-29T11:08:48+00:00

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/*.py: Typo fixes/grammar/comment fixes, nothing functional.

2014-08-25T07:57:45+00:00

(Bitbake rev: 587b144ee409d444494d8d7f2d1c53ede8f7c953) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

bitbake: monitordisk: lower inode check warning to note

2013-10-18T15:02:16+00:00

Filesystems like btrfs and reiserfs sets the inode count to 0, since they don't have an inode concept. This is expected, and having a warning show up every time you run bitbake can cause undue concern. (Bitbake rev: f3ac2d3678f48c68a250a0a20c08cf8687322d38) Signed-off-by: Olof Johansson Signed-off-by: Richard Purdie

bitbake: lib/bb/monitordisk.py: fix spelling in error text

2013-10-02T14:41:21+00:00

(Bitbake rev: 78efda1224a99ed3d2ca6befb9fd719d82f6b0ae) Signed-off-by: Erik Botö Signed-off-by: Richard Purdie

bitbake: monitordisk.py: disable inode checking for btrfs

2013-04-15T14:57:31+00:00

The btrfs doesn't have static inode, so disable the inode check for it, the previouse patch has set it: minInode = None But this is incorrect, the minInode is just a temporary variable, it should be: self.devDict[k][2] = None [YOCTO #3609] (Bitbake rev: 7e45149c292bc92314af9b42962fde8f603a179f) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: monitordisk.py: monitor disks based on path

2013-03-19T13:55:38+00:00

The previous monitor is based on the disk, and one disk only can have one action, this limits its function, for example we set this in the current local.conf: BB_DISKMON_DIRS = "\ STOPTASKS,${TMPDIR},1G,100K \ STOPTASKS,${DL_DIR},1G,100K \ STOPTASKS,${SSTATE_DIR},1G,100K \ ABORT,${TMPDIR},100M,1K \ ABORT,${DL_DIR},100M,1K \ ABORT,${SSTATE_DIR},100GM,1K" Before: * If TMPDIR, DL_DIR and SSTATE_DIR are on the same disk partition, only the last line "ABORT,${SSTATE_DIR},100GM,1K" works * If TMPDIR, DL_DIR and SSTATE_DIR are on the different disk partitions, only the last three lines (ABORT) work. These are not what we expect, now: * We monitor the disk based on the path and action, so all the six lines will work no matter whether they are on the same disk partition or not. * The out put format will be: WARNING: The free space of /path/to/directory (device) is running low (XXGB left) [YOCTO #3995] (Bitbake rev: e22a576672ee4a40b44f7a826a78a77fc07e9177) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: monitordisk.py: disable the inode checking for some fs

2013-02-15T12:12:36+00:00

There is an error when use disk monitor on btrfs: WARNING: The free inode of rootfs is running low (0.000K left) ERROR: Immediately abort since the disk space monitor action is "ABORT"! This is beucase some fs formats' statvfs.f_files (inodes) is zero, thus the statvfs.f_favail (free inodes) is zero, too, this a feature of the fs, we disable the inode checking for such a fs. [YOCTO #3609] (Bitbake rev: b2ada3ad5f7aefff107f013e0c9decea481c7ef6) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: monitordisk: fire event DISKFULL when terminate build

2012-08-02T14:28:39+00:00

Part of [Yocto #2168] Add a event DiskFull to descript the termination by disk monitor. Update check() to fire the event DiskFull when terminates the build. This could help UIs to deal this scenario and show more information to end user. (Bitbake rev: 0a0fca3d94a1db6458ae21501a66461a334410ed) Signed-off-by: Kang Kai Signed-off-by: Richard Purdie

diskspace monitor: assign a default value when only of the interval is set

2012-04-10T23:04:40+00:00

Assign a default value to the other one when either disk space interval or amount of inodes interval value is set for example: BB_DISKMON_WARNINTERVAL = "50M," or BB_DISKMON_WARNINTERVAL = ",5K" The diskspace monitor would not enable in the past, that seemed unreasonable, assign a default value to the other one currently, so the monitor will be enabled, and will warn both of diskspace and free amount of inode if they have been set in BB_DISKMON_DIRS. (Bitbake rev: 09592c119550550edcc59c871f754536d5b7bf65) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

meta/classes: Convert to use appendVar and appendVarFlags

2012-03-05T18:36:53+00:00

(From OE-Core rev: 3b57de68e70e77dbc03c0616a83a29a2e99e40b4) Signed-off-by: Richard Purdie