https://luci-milo.appspot.com/buildbot/chromeos/wolf-tot-paladin/9974
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/116750019-chromeos-test/chromeos4-row1-rack4-host17/debug/

05/10 13:08:43.714 INFO |            repair:0327| Verifying this condition: Did not find critical file system errors
05/10 13:08:43.714 DEBUG|          ssh_host:0284| Running (ssh) 'dmesg | grep -E "EXT4-fs error \(device $(cut -d ' ' -f 5,9 /proc/$$/mountinfo | grep -e '^/mnt/stateful_partition ' | cut -d ' ' -f 2 | cut -d '/' -f 3)\):"'
05/10 13:08:44.008 DEBUG|             utils:0297| [stdout] [    5.886337] EXT4-fs error (device sda1): empty_dir:2525: inode #16959: comm rmdir: error -5 reading directory lblock 2
05/10 13:08:44.012 ERROR|            repair:0332| Failed: Did not find critical file system errors
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/hosts/repair.py", line 329, in _verify_host
    self.verify(host)
  File "/usr/local/autotest/server/hosts/cros_repair.py", line 130, in verify
    raise hosts.AutoservVerifyError(message)
AutoservVerifyError: Saw file system error: [    5.886337] EXT4-fs error (device sda1): empty_dir:2525: inode #16959: comm rmdir: error -5 reading directory lblock 2
05/10 13:08:44.014 INFO |        server_job:0184| 	FAIL	----	verify.ext4	timestamp=1494446924	localtime=May 10 13:08:44	Saw file system error: [    5.886337] EXT4-fs error (device sda1): empty_dir:2525: inode #16959: comm rmdir: error -5 reading directory lblock 2