New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 675784 link

Starred by 1 user
Status: WontFix
Owner:
█ sbasi@chromium.org
Last visit > 30 days ago
Closed: Jan 2017
Cc:
akes...@chromium.org
dgarr...@chromium.org
█ nxia@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

CommitQueueSync Failure: Device or resource busy

Project Member Reported by sbasi@chromium.org, Dec 20 2016 
This hit the CQ

https://uberchromegw.corp.google.com/i/chromeos/builders/x86-zgb-paladin/builds/8501/steps/CommitQueueSync/logs/stdio

@@@STEP_FAILURE@@@
15:25:10: ERROR: <class 'chromite.lib.cros_build_lib.RunCommandError'>: return code: 1; command: sudo -n 'CROS_CACHEDIR=/b/cbuild/internal_master/.cache' 'CROS_SUDO_KEEP_ALIVE=unknown' -- rm -rf -- /b/cbuild/internal_master/chroot
rm: cannot remove `/b/cbuild/internal_master/chroot/dev': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/run': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/proc': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/mnt/host/depot_tools': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/mnt/host/source': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/home/chrome-bot/.cidb_creds': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/home/chrome-bot/.subversion': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/var/cache/chromeos-cache': Device or resource busy
rm: cannot remove `/b/cbuild/internal_master/chroot/sys': Device or resource busy


NingNing/Don, any thoughts?

Comment 1 by nxia@chromium.org, Dec 20 2016 

haven't saw this issue before. Logged in to that machine but didn't find any opened files under '/b/cbuild/internal_master/chroot/'.

manually run 'sudo -n 'CROS_CACHEDIR=/b/cbuild/internal_master/.cache' 'CROS_SUDO_KEEP_ALIVE=unknown' -- rm -rf -- /b/cbuild/internal_master/chroot' and it succeeded. let's see what will happen in the next run.

Comment 2 by dgarr...@chromium.org, Jan 12 2017

Status: WontFix (was: Untriaged)
It seems to have gone away on it's own.

It looks like the chroot was in use (and so all those locations were bind mounted to various things) while we attempted to clean it up.

Rebooting (which we do after every build) would have cleared that up, but I'm curious why it was left in that state. No way to debug it now.
►

Sign in to add a comment