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

Issue 770593 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
kinaba@chromium.org
fukino@chromium.org
█ uekawa@chromium.org
hashimoto@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Migration failed due to account already mounted

Project Member Reported by dspaid@chromium.org, Oct 2 2017 
Feedback report 74641772716

I'm not entirely sure what is happening here.  Cryptohome logs seem to indicate that the account was originally not mounted and so it starts going through the migration UI, but some point before actually mounting for migration the directory is mounted and the subsequent mount for migration ends up being a no-op as it goes through the mount exists code path[1].  I have no idea how this happened, but we could probably make mount_for_migration do something more intelligent in this case.

1: https://chromium.git.corp.google.com/chromiumos/platform2/+/58c65f95b39a8daec19b3993c784d13bd1cfaee8/cryptohome/service.cc#1962

Comment 1 by kinaba@chromium.org, Oct 2 2017 

One scenario I could came up with is clicking both the "skip" and "update" buttons
before the wizard screen goes away (Bug 763211), and this pattern is fixed by fukino@ for M61.


But this repro step does not pop up a feedback dialog, so there has to be other cause (which I and fukino@ is failing to find out so far.)

> but we could probably make mount_for_migration do something more intelligent in this case.

not sure if we want to do this. Home directly "normally" mounted very likely means that some process started accessing the content. Unless we know exactly what is happening, we cannot assume it safe to do migration after the event.

Comment 2 by zalcorn@chromium.org, Dec 27 2017

Components: Platform>ARC

Comment 3 by efoo@chromium.org, Jul 6

Components: Platform>Apps>ARC
►

Sign in to add a comment