provision_AutoUpdate failed: Cannot mkdir: No space left on device |
|||||||||
Issue descriptionprovision_AutoUpdate failed, can't perform stateful update on device. In the log, tons of error like: 06/10 12:05:36.886 DEBUG| base_utils:0278| [stdout] tar: var_new/db/pkg/virtual/assets-1.5-r1/SLOT: Cannot open: No such file or directory 06/10 12:05:36.886 DEBUG| base_utils:0278| [stdout] tar: var_new: Cannot mkdir: No space left on device 06/10 12:05:36.886 DEBUG| base_utils:0278| [stdout] tar: var_new/db/pkg/virtual/assets-1.5-r1/BUILD_TIME: Cannot open: No such file or directory 06/10 12:05:36.886 DEBUG| base_utils:0278| [stdout] tar: var_new: Cannot mkdir: No space left on device 06/10 12:05:36.886 DEBUG| base_utils:0278| [stdout] tar: var_new/db/pkg/virtual/assets-1.5-r1/assets-1.5-r1.ebuild: Cannot open: No such file or directory 06/10 12:05:36.886 DEBUG| base_utils:0278| [stdout] tar: var_new: Cannot mkdir: No space left on device https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/66371572-chromeos-test/chromeos2-row1-rack7-host5/debug/
,
Jun 10 2016
,
Jun 10 2016
interesting errors. Assign to myself to remind me handle this case in new auto-update framework.
,
Jun 10 2016
,
Jun 10 2016
Looking at ./client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py It looks like there is not code to remove output_path nit. in_cloud parameter should be documented as well. I can't ssh the machine anymore, I wonder how the results directory could have ballooned to 5GB.
,
Jun 10 2016
Taking care of the output file part.
,
Jun 11 2016
Autotest is supposed to automatically fix this kind of problem. Unfortunately, the "do we have enough space?" check needs to require more free space. That's detailed in bug 614898. The fix is easy in theory, except that it could break rialto. That said, after provision failed, the DUT should have repaired automatically, but it didn't...
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 12 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 12 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by gwendal@chromium.org
, Jun 10 2016