New issue
Advanced search Search tips

Issue 637890 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

BuildImage stage failed on M53 Samus PFQ builder with Failed to write to output filesystem

Project Member Reported by keta...@chromium.org, Aug 15 2016

Issue description

Write failed because No space left on device

FATAL ERROR:Failed to write to output filesystem
Parallel mksquashfs: Using 32 processors
Creating 4.0 filesystem on /mnt/host/source/src/build/images/samus/R53-8530.57.0-rc1/rootfs/opt/google/containers/android/vendor.raw.img, block size 131072.
INFO    : Unmounting image from /mnt/host/source/src/build/images/samus/R53-8530.57.0-rc1/stateful and /mnt/host/source/src/build/images/samus/R53-8530.57.0-rc1/rootfs
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/samus/R53-8530.57.0-rc1/stateful/dev_image
An error occurred in your build so your latest output directory is invalid.
Running in non-interactive mode so deleting output directory.
Deleted /mnt/host/source/src/build/images/samus/R53-8530.57.0-rc1
01:21:08: ERROR: 
return code: 1; command: /b/cbuild/shared_internal/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpdCKDYT' 'USE=chrome_internal' 'FEATURES=separatedebug' 'CHROME_ORIGIN=LOCAL_SOURCE' -- ./build_image '--board=samus' --replace '--version=8530.57.0-rc1' test
cwd=/b/cbuild/shared_internal, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmpdCKDYT', 'USE': 'chrome_internal', 'FEATURES': 'separatedebug', 'CHROME_ORIGIN': 'LOCAL_SOURCE'}


Link to log - https://uberchromegw.corp.google.com/i/chromiumos.release/builders/samus-pre-flight-branch%20release-R53-8530.B/builds/105/steps/BuildImage/logs/stdio

Xixuan@ can we look into this branch builder's running out of space problem? We are seeing something similar on the cyan builder for trunk as well. jamescook@ please link the issue for that builder when ready.
 
Above failure is on slave build304-m2

cyan failure is  issue 637900  on slave cros-beefy191-c2
build304-m2 had 2.5TB of free space.

The "out of space" issue was with the rootfs partition on the image, not the builder.

There was a recent bug fix for this in the squashfs image generation process, if you can find it, it might be worth merging to R53. 
Looks like Issue 630426 indeed. I'll request a 53 merge, sorry about that.
Mergedinto: 630426
Status: Duplicate (was: Untriaged)

Sign in to add a comment