[bitbake-devel] [PATCH 0/2] V2 Disk space monitoring

[Chris Larson]

On Tue, Jan 10, 2012 at 5:45 AM, Robert Yang <liezhi.yang at windriver.com> wrote:
> Here are the test info:
> 1) set the following variables in conf/local.conf for testing:
>   BB_DISKMON_DIRS = "${TMPDIR} ${DL_DIR} ${SSTATE_DIR} /home/lyang1"
>   BB_DISKMON_MINSPACE = "200G"
>   BB_DISKMON_MININODES = "20M"
>   BB_DISKMON_INTERVAL = "30s"
>
>   The TMPDIR, DL_DIR and SSTATE_DIR are in the same disk(/dev/sdb4) in
>   my build, so I added another direcotory /home/lyang1 to test the
>   ability of monitoring multi mount points.
>
> 2) bitbake core-image-sato
>   WARNING: The free space of /dev/sdb5 is running low (25.915GB left)
>   WARNING: The free inode of /dev/sdb5 is running low (1788.202K left)
>   WARNING: The free space of /dev/sdb4 is running low (189.309GB left)
>   WARNING: The free inode of /dev/sdb4 is running low (18005.443K left)
>
> 3) Aalso have tested about the following items:
>   a) Use ctrl-c to stop the monitor
>   b) The monitor should stop when the build stops
>   c) Test the space unit G, B, K(case in-sensitive) and the time unit
>      h, m, s(case-sensitive)

I would think it'd be more useful to be able to specify the thresholds
on a per-mountpoint or per-path basis. The space needed by sstate,
downloads, and the rest of the build can be quite different. Further,
the space requirements for DL_DIR and sstate both are dependent upon
the current contents of the directories, as if we already have all our
downloads, the free space there isn't much of a concern..
-- 
Christopher Larson