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

Issue 801984 link

Starred by 2 users
Status: Assigned
Owner:
█ bartfab@chromium.org
Working on ARC now
Cc:
apronin@chromium.org
█ rspangler@chromium.org
gwendal@chromium.org
█ cyrusm@chromium.org
igorcov@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Repeated drop to recovery mode results in FS corruption

Project Member Reported by atwilson@chromium.org, Jan 15 2018 
There are countless bugs filed whose root cause is "continually Esc-Refresh-Power until file system is corrupted" (example, crbug.com/787970).

We should figure out how to reduce the incidence of this - either by flushing FS writes before restarting (maybe hard to do since the whole point of refresh-power is to do a hard reboot), or by having some way to clean up or repair the file system.

Comment 1 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)

Comment 2 by atwilson@chromium.org, Sep 4

Owner: bartfab@chromium.org
I don't think this bug is actionable in its current state, but gonna pass the buck anyway to have it on the enterprise-platform team's radar.

Comment 3 by bartfab@chromium.org, Sep 4 

I agree that we should not be flushing on Esc-Refresh-Power as the whole point is an instantaneous restart.

I think we should detect signs of such corruption, try to repair (do we not fsck?) and if the FS is beyond repair, do a wipe and drop the user into forced re-enrollment.
►

Sign in to add a comment