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

Issue 715932 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

amd64-generic-chromium-pfq fails VMtests with "no space left on device"

Project Member Reported by mnissler@chromium.org, Apr 27 2017

Issue description

First build failing:

https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-generic-chromium-pfq/builds/10007

Stateful file system size is dropping from 4G in the R60-9494.0.0-rc1 run to 1.2G in the R60-9495.0.0-rc1 run.

Likely culprit: https://chromium-review.googlesource.com/c/486248/
 
Confirmed, aforementioned CL switches the disk layout from 2gb-rootfs-updateable to 4gb-rootfs. The former has 4gb stateful, the latter only 1.2. I'll send a CL to increase the stateful size to 4gb for 4gb-rootfs. Shouldn't have any adverse effects since 4gb-rootfs is only used for amd64-generic builders.
Here's the suggested fix: https://chromium-review.googlesource.com/488361
I've meanwhile discovered that gurchetansingh@ has an alternative fix up for review at https://chromium-review.googlesource.com/c/484814/ but it's more complicated due to the current behavior of the inheritance logic.
Turns out that my fix in comment #2 isn't sufficient as it just bumps up stateful size, the CL in comment #3 (or an alternative) is required as well to address the issue of a too-small rootfs getting created.
Cc: chadversary@chromium.org

Comment 6 by warx@chromium.org, Apr 27 2017

Mergedinto: 715702
Status: Duplicate (was: Available)
I will dup this into issue 715702.

Sign in to add a comment