New issue
Advanced search Search tips

Issue 905862 link

Starred by 1 user
Status: Closed
Owner:
zamorzaev@chromium.org
Closed: Nov 16
Cc:
benchan@chromium.org
jclinton@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

rmdir: error -5 reading directory lblock 0

Project Member Reported by zwisler@google.com, Nov 15 
Failed wolf-release build:

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929768258873249472

Failed during HWTest provisioning with these messages:

  provision              FAIL: Saw file system error: [    7.146382] EXT4-fs error (device sda1): empty_dir:2483: inode #520279: comm rmdir: error -5 reading directory lblock 0, completed successfully

Comment 1 by zamorzaev@chromium.org, Nov 15

Labels: Hotlist-Deputy OS-Chrome
Looks like the same exact thing happened on wolf more than a year ago ( issue 721002 ). The last time it went away on its own.

My guess that this is a wolf-specific flake. If my guess is correct, it shouldn't happen on the next run. Let's monitor the next run and if it is OK close the bug.

The dut (chromeos4-row1-rack3-host9) is currently healthy.

Comment 2 by afakhry@google.com, Nov 16

Components: Infra>Client>ChromeOS

Comment 3 by zwisler@google.com, Nov 16

Status: Closed (was: Untriaged)
We've had 2 green runs since this failure occurred.  

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929738240634642336

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929707796265816944

Chalking it up to an intermittent flake, and closing bug.
►

Sign in to add a comment