Storm of "Valid eCryptfs headers not found in file header region or xattr region" messages |
|||
Issue descriptionChrome Version: 54.0.2840.13 Chrome OS Version: 8743.11.0 Chrome OS Platform: elm From: https://feedback.corp.google.com/#/Report/21300270540 Steps To Reproduce: (1) Device crashed (2) Reboot (3) Inspect dmesg Expected Result: Actual Result: dmesg starts with the "Valid eCryptfs headers" storm. Note, that there were so many of these messages that the dmesg is truncated, so any earlier messages were lost. ... [ 22.698770] Valid eCryptfs headers not found in file header region or xattr region, inode 261921 [ 22.699597] Valid eCryptfs headers not found in file header region or xattr region, inode 261839 [ 22.700307] Valid eCryptfs headers not found in file header region or xattr region, inode 261917 [ 22.703872] Valid eCryptfs headers not found in file header region or xattr region, inode 261813 [ 22.704558] Valid eCryptfs headers not found in file header region or xattr region, inode 261849 [ 22.705209] Valid eCryptfs headers not found in file header region or xattr region, inode 261863 [ 22.705902] Valid eCryptfs headers not found in file header region or xattr region, inode 261909 [ 22.706521] Valid eCryptfs headers not found in file header region or xattr region, inode 261809 [ 22.707144] Valid eCryptfs headers not found in file header region or xattr region, inode 261897 [ 22.711595] Valid eCryptfs headers not found in file header region or xattr region, inode 134287 [ 22.712426] Valid eCryptfs headers not found in file header region or xattr region, inode 261859 [ 22.713171] Valid eCryptfs headers not found in file header region or xattr region, inode 134295 [ 22.723551] Valid eCryptfs headers not found in file header region or xattr region, inode 132729 [ 22.727688] Valid eCryptfs headers not found in file header region or xattr region, inode 132735 [ 22.729825] Valid eCryptfs headers not found in file header region or xattr region, inode 132737 [ 22.732114] Valid eCryptfs headers not found in file header region or xattr region, inode 132736 How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) There have been similar reports over the years, usually associated with hard crashes / sudden shutdowns. issue 217829 issue 258142 http://crosbug.com/p/53119 http://crosbug.com/p/52831 http://crosbug.com/p/57396 What is the impact to the user, and is there a workaround? If so, what is it? I'd like to confirm that this is normal behavior after a hard crash and completely recoverable.
,
Nov 18 2016
Gwendal? Yes, I think we've seen the issue for a long time. I believe we should recover correctly in userspace -- is there any other issue besides the strange error messages?
,
Nov 20 2017
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 2 2018
Is this still an issue? Please close if this is no longer valid. |
|||
►
Sign in to add a comment |
|||
Comment 1 by akhal...@gmail.com
, Nov 18 2016