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

Issue 797015 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

provision fails because stateful partition is out of space

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 21 2017

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of bmgordon@google.com

I've seen this across a couple of boards, but here is today's:

gandof-release:1770 failed

Builders failed on: 
- gandof-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/gandof-release/1770

While attempting to provision, the stateful partition seems to be out of space:

2017/12/21 04:58:44.093 INFO |      auto_updater:0777| Updating stateful partition with clobber enabled...
2017/12/21 04:58:44.093 DEBUG|    cros_build_lib:0593| RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpvZZNTZ/testing_rsa root@chromeos4-row5-rack6-host15 -- sh /mnt/stateful_partition/unencrypted/preserve/cros-update/tmp.7WplLyogdo/stateful_update /mnt/stateful_partition/unencrypted/preserve/cros-update/tmp.7WplLyogdo/stateful.tgz '--stateful_change=clean'
Warning: Permanently added 'chromeos4-row5-rack6-host15,100.115.196.74' (ED25519) to the list of known hosts.
Warning: Permanently added 'chromeos4-row5-rack6-host15,100.115.196.74' (ED25519) to the list of known hosts.
Reading local payload /mnt/stateful_partition/unencrypted/preserve/cros-update/tmp.7WplLyogdo/stateful.tgz
tar: dev_image_new/lib64/libmagic.so.1.0.0: Cannot write: No space left on device
tar: dev_image_new/lib64/libMagickCore-6.Q16.so.3.0.0: Cannot write: No space left on device
...

The immediately following repair shows some dmesg entries that look like a possible disk error:

[   25.220150] loop: Write error at byte offset 1623420928, length 4096.
[   25.221083] EXT4-fs warning (device dm-1): ext4_end_bio:336: I/O error -28 writing to inode 95722 (offset 0 size 4096 starting block 396343)
[   25.221100] Buffer I/O error on device dm-1, logical block 396343
[   25.253975] loop: Write error at byte offset 1621233664, length 4096.
[   25.253994] EXT4-fs warning (device dm-1): ext4_end_bio:336: I/O error -28 writing to inode 95742 (offset 0 size 12288 starting block 395809)
[   25.254009] Buffer I/O error on device dm-1, logical block 395809
[   25.254018] Buffer I/O error on device dm-1, logical block 395810
[   25.254026] Buffer I/O error on device dm-1, logical block 395811
[   25.287510] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   25.293296] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   25.299076] loop: Write error at byte offset 1623425024, length 4096.
[   25.299096] EXT4-fs warning (device dm-1): ext4_end_bio:336: I/O error -28 writing to inode 95744 (offset 0 size 4096 starting block 396344)
[   25.299111] Buffer I/O error on device dm-1, logical block 396344
[   25.300270] loop: Write error at byte offset 1621245952, length 4096.
[   25.300286] EXT4-fs warning (device dm-1): ext4_end_bio:336: I/O error -28 writing to inode 95745 (offset 0 size 4096 starting block 395812)
[   25.300301] Buffer I/O error on device dm-1, logical block 395812

http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos4-row5-rack6-host15/1091189-repair/

 
Cc: martinroth@chromium.org jrbarnette@chromium.org bmgordon@chromium.org
Components: Infra>Client>ChromeOS
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Sign in to add a comment