9459 2016-04-13 20:14:38 +0000 We should add IGNORE as an option for the diskmonitor so that a user can override what the system wants to do 2016-04-14 16:28:40 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 2.2 x86 Multiple RESOLVED NOTABUG Medium enhancement 2.2 1 brian.avery brian.avery poky.bs.watcher poky.watcher --- --- Yes (doc changes required) oldest_to_newest 61175 0 brian.avery 2016-04-13 20:14:38 +0000 We currently only allow "ABORT", "STOPTASKS", "WARN" for actions. This means that even if I know that my mount point is ok, I can't tell the system to leave it alone. We should either allow IGNORE for the action or add a Variable to disable the monitor altogether. To add IGNORE, all we need to do is : change bitbake/lib/bb/monitordisk.py - if action not in ("ABORT", "STOPTASKS", "WARN"): to - if action not in ("ABORT", "STOPTASKS", "WARN", "IGNORE"): Nicely, all of the action dispatch code checks for keyword matches, but we should probably add an: elif action == "IGNORE": pass just to be clear. ----- Why this mattered to me: I'm running on a Docker container inside a VM on MacOSX. My sstate is in a bind (effectively) mounted OSX dir which the container can see. bitbake is unhappy with the inode number; but because of the odd driver being used, that number does not reflect reality. With the explosion of filesystems, I'd prefer to have an override option in case the user does know better. 61199 1 richard.purdie 2016-04-14 12:43:59 +0000 Why wouldn't you just not list this in BB_DISKMON_DIRS at all? 61227 2 richard.purdie 2016-04-14 15:08:28 +0000 See above question... 61240 3 brian.avery 2016-04-14 16:27:42 +0000 because I didn't see that I could. My bad. 61241 4 brian.avery 2016-04-14 16:28:40 +0000 Didn't realize how I should have overridden this.