New issue
Advanced search Search tips

Issue 852876 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 1
Type: Bug



Sign in to add a comment

Fuchsia SDK roll blocked by extend_fvm.py failure

Project Member Reported by w...@chromium.org, Jun 14 2018

Issue description

In the attempted SDK roll at https://chromium-review.googlesource.com/c/chromium/src/+/1098518 we started getting compile step failures while executing extend_fvm.py:

[156/20685] ACTION //build/config/fuchsia:blobstore_extended_fvm(//build/toolchain/fuchsia:x64)
FAILED: fvm.extended.blk 
python ../../build/config/fuchsia/extend_fvm.py /b/swarming/w/ir/cache/builder/src/third_party/fuchsia-sdk/sdk/tools/fvm /b/swarming/w/ir/cache/builder/src/third_party/fuchsia-sdk/sdk/target/x64/fvm.blk /b/swarming/w/ir/cache/builder/src/out/Release/fvm.extended.blk 1073741824
check: detected inode 6 with bad state
check: detected inode 60 with bad state
check: detected inode 64 with bad state
check: detected inode 65 with bad state
check: detected inode 71 with bad state
check: detected inode 77 with bad state
check: detected inode 78 with bad state
check: detected inode 80 with bad state
check: detected inode 84 with bad state
check: detected inode 94 with bad state
check: detected inode 106 with bad state
check: detected inode 113 with bad state
check: detected inode 141 with bad state
check: detected inode 143 with bad state
check: detected inode 144 with bad state
check: detected inode 148 with bad state
check: detected inode 160 with bad state
check: detected inode 180 with bad state
check: detected inode 183 with bad state
check: detected inode 187 with bad state
check: detected inode 198 with bad state
check: detected inode 201 with bad state
check: detected inode 208 with bad state
check: detected inode 224 with bad state
check: detected inode 226 with bad state
check: detected inode 237 with bad state
check: detected inode 238 with bad state
check: detected inode 239 with bad state
check: detected inode 255 with bad state
check: detected inode 268 with bad state
check: detected inode 281 with bad state
check: detected inode 283 with bad state
check: detected inode 290 with bad state
check: detected inode 291 with bad state
check: detected inode 292 with bad state
check: detected inode 294 with bad state
check: detected inode 301 with bad state
check: detected inode 315 with bad state
check: detected inode 317 with bad state
blobfs fsck returned an error.
Verify failed - cancelling extension
Traceback (most recent call last):
  File "../../build/config/fuchsia/extend_fvm.py", line 26, in <module>
    sys.exit(ExtendFVM(*sys.argv[1:]))
  File "../../build/config/fuchsia/extend_fvm.py", line 22, in ExtendFVM
    str(new_size)])
  File "/b/swarming/w/ir/cipd_bin_packages/lib/python2.7/subprocess.py", line 186, in check_call
    raise CalledProcessError(retcode, cmd)
 
The "fvm.blk" volume in SDK build 2a3f9cee854422c4ce6e1a2fbae297777e390fc2 is bad and failures to extend or verify. Another explanation is that the volume might be fine, but the "blobfs fsck" could be buggy.

Filed Fuchsia bug DX-255.
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 16 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd

commit 40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd
Author: Kevin Marshall <kmarshall@chromium.org>
Date: Sat Jun 16 01:33:55 2018

Fuchsia: Roll Fuchsia SDK from 2ddc73f to ad481e2.

* Fix to broken host tool "fvm verify" tested (outcome: works).
* SDK method rename; "zx_get_startup_handle" to "zx_take_startup_handle".

Bug:  852876 ,707030
Change-Id: Ib635c807ae92dedc76c65c34ab9d3829e8a7e5c0
Reviewed-on: https://chromium-review.googlesource.com/1102834
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567853}
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/base/fuchsia/services_directory.cc
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/base/process/launch.h
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/base/process/process_util_unittest.cc
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/build/fuchsia/sdk.sha1
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/mojo/edk/embedder/platform_channel_pair_fuchsia.cc
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/mojo/public/cpp/platform/platform_channel.cc
[modify] https://crrev.com/40dc4360fbc783de3e0ce5bb21bf5d25d16e9ebd/third_party/crashpad/crashpad/handler/handler_main.cc

Status: Verified (was: Assigned)
Root cause was the fvm host tool not being updated when compressed blob support was deployed.

Sign in to add a comment