Issue 638257 link

Starred by 1 user

Issue metadata

Status:	Archived
Owner:	xixuan@chromium.org
Closed:	Aug 2016
Cc:	█ pho...@chromium.org █ shuqianz@chromium.org dgarr...@chromium.org saintlou@google.com josa...@google.com puneetster@google.com
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	0
Type:	Bug
VerifyIn-55 VerifyIn-56 VerifyIn-57 VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Trouble on chromeos-server74.cbf - cave shard

Reported by jrbarnette@chromium.org, Aug 16 2016

Issue description

This morning's lab inventory failed when it got to cave; there
were '500' errors reported on the dut status rpc call.

I ran this command manually:
   dut-status -b cave

And go the same 500 error.

Logging in to the shard, and poking around, I discovered this:
    $ df -k /tmp
    Filesystem     1K-blocks      Used Available Use% Mounted on
    /dev/xvda1     511991720 487576852         0 100% /

Comment 1 by jrbarnette@chromium.org, Aug 16 2016

The problem is in /usr/local/autotest/results:

    $ cd /usr/local/autotest/results
    $ du -sm .
    459572	.
    $ df -m .
    Filesystem     1M-blocks   Used Available Use% Mounted on
    /dev/xvda1        499992 476152         0 100% /usr/local/autotest
    $ du -sm * | sort -n | tail -10
    6393	73011543-chromeos-test
    6393	73011545-chromeos-test
    6393	73011547-chromeos-test
    6394	73011539-chromeos-test
    6395	73011497-chromeos-test
    6395	73011506-chromeos-test
    6396	73011527-chromeos-test
    6543	72756151-chromeos-test
    6543	72756153-chromeos-test
    6544	72756152-chromeos-test

All of the tests are wifi tests.  The results directories have some
very large crashinfo directories, among other things.

Project Member

Comment 2 by sheriffbot@chromium.org, Aug 31 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot