My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 204997: Alex canary failed with disk errors, though there was enough space
1 person starred this issue and may be notified of changes. Back to list
Status:  WontFix
Moved from:  issue chromium-os:21955
Owner:  sosa@chromium.org
Closed:  Oct 2011
Cc:  sosa@chromium.org


Sign in to add a comment
 
Project Member Reported by dianders@chromium.org, Oct 21, 2011
The x86-alex canary build (1156) failed with "No space left on device" at roughly Fri Oct 21 11:00:19 2011:

Here's the extracted error

  Extracting autotest from build artifacts...
  tar: autotest/client/deps/chrome_test/test_src/chrome/test/data/profiles/typical_history/Default/History: Wrote only 5120 of 10240 bytes
  tar: autotest/client/site_tests/platform_ToolchainOptions/src/gas/config/xtensa-relax.c: Wrote only 4608 of 10240 bytes
  tar: autotest/client/site_tests/platform_ToolchainOptions/src/gas/config/obj-som.h: Cannot write: No space left on device
  tar: autotest/client/siProcess BackgroundSteps-2:4:
  Traceback (most recent call last):
    File "/usr/lib/python2.6/multiprocessing/process.py", line 232, in _bootstrap
      self.run()
    File "/b/build/slave/x86-alex-canary-master/build/chromite/buildbot/cbuildbot_background.py", line 101, in run
      traceback.print_exc(file=sys.stderr)
    File "/usr/lib/python2.6/traceback.py", line 227, in print_exc
      print_exception(etype, value, tb, limit, file)
    File "/usr/lib/python2.6/traceback.py", line 124, in print_exception
      _print(file, 'Traceback (most recent call last):')
    File "/usr/lib/python2.6/traceback.py", line 13, in _print
      file.write(str+terminator)
  IOError: [Errno 28] No space left on device

...but when kliegs logged into "chromeosbuild", he saw that there was enough space.  IRC log:

  (11:22:06 AM) kliegs: hmm. machine has 13gb free on root
  (11:22:11 AM) kliegs: and 161gb free on /b
  (11:22:18 AM) kliegs: ellyjones: build2?
  (11:22:28 AM) ellyjones: http://chromeos-botmaster.mtv.corp.google.com:8026/buildslaves/chromeosbuild2 this guy
  (11:23:55 AM) kliegs: hmm.  its got lots of space
  (11:25:09 AM) kliegs: did anyone else free up spay on chromeosbuild2?
  (11:26:31 AM) kliegs: s/spay/space
  (11:29:25 AM) kliegs: i'm showing enough space on the device.  the directory it was writing to only need half a gig more and there's more
  (11:34:13 AM) kliegs: dianders: i'm not seeing it being low enough on space to have triggered those messages

Oct 21, 2011
#1 kliegs@chromium.org
From looking at disk space on it:

chrome-bot@chromeosbuild2:/var/www/archive/x86-alex-release$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md0               56G   40G   13G  76% /
none                  5.9G  528K  5.9G   1% /dev
none                  5.9G   12K  5.9G   1% /dev/shm
none                  5.9G   52K  5.9G   1% /var/run
none                  5.9G     0  5.9G   0% /var/lock
none                  5.9G     0  5.9G   0% /lib/init/rw
/dev/md1              404G  213G  171G  56% /b

And an du -sh of /var/www/archive/x86-alex-release


chrome-bot@chromeosbuild2:/var/www/archive/x86-alex-release$ du -sh *
4.0K	LATEST
3.9G	R16-1199.0.0-a1-b1149
3.9G	R17-1200.0.0-a1-b1150
3.9G	R17-1201.0.0-a1-b1151
3.1G	R17-1204.0.0-a1-b1153
3.2G	R17-1205.0.0-a1-b1154
3.1G	R17-1207.0.0-a1-b1155
2.6G	R17-1208.0.0-a1-b1156

It looks like there's space.  Unless the intermediary steps use an extra 10gb.  


Owner: ---
Cc: sosa@chromium.org
Nov 11, 2011
#2 davidjames@google.com
10gb isn't enough -- let's just make sure we have lots of space on our machines :)
Status: WontFix
Mar 6, 2013
#3 lafo...@google.com
(No comment was entered for this change.)
Labels: OS-Chrome
Mar 9, 2013
#4 bugdroid1@chromium.org
(No comment was entered for this change.)
Labels: -Area-Build -TreeCloser Build Hotlist-TreeCloser
Sign in to add a comment

Powered by Google Project Hosting