New issue
Advanced search Search tips

Issue 818421 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 689605
Owner:
Closed: Jul 2
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
ExternalMedia-Mounting


Sign in to add a comment

Files App doesn't fully eject devices from the entire system.

Reported by cjmwarfi...@gmail.com, Mar 3 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10176.72.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36
Platform: 10176.72.0 (Official Build) stable-channel falco

Steps to reproduce the problem:
1. Install the Chromebook Recovery Utility (https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai)
2. Insert a USB stick, and then eject it using the files app.
3. Open the recovery utility, and the USB stick should still be available to use for creating a recovery medium even though it has been ejected.

What is the expected behavior?
The USB stick shouldn't be available for creating a recovery medium as it has been ejected.

What went wrong?
The USB stick was still available - showing that it hasn't been fully ejected from the entire system.

Did this work before? No 

Chrome version: 64.0.3282.167  Channel: stable
OS Version: 64.0.3282.167 (Official Build) (64-bit)
Flash Version: 28.0.0.161
 
Components: Platform>Apps>FileManager
Status: Untriaged (was: Unconfirmed)
repro'd on 67.0.3365.0.

Comment 3 by sashab@chromium.org, Mar 15 2018

Labels: -Pri-2 CrOSFilesCategory-ExternalMedia Pri-3
Status: Available (was: Untriaged)

Comment 4 by sashab@chromium.org, Apr 19 2018

Labels: -CrOSFilesCategory-ExternalMedia CrOSFilesFeature-ExternalMedia

Comment 5 by sashab@google.com, Jun 5 2018

Owner: amistry@chromium.org
Status: Assigned (was: Available)
cros-disks ejects a device by first unmounting it, then calling the 'eject' command. But eject doesn't do anything useful for disks, only for CD/Floppy/Jazz/Tape/<other ancient physical mediums>. So the device is still accessible for the recovery utility, or even to remount the disk if the UI existed.

If what is meant by eject is to make it safe to remove, the current behaviour is correct. If eject is supposed to mean "remove device from system", then a change is needed. The change would be to use 'udisksctl' to power-off the device, which logically disconnects the USB device and turns off the power. The only way to reset is to issue a USB device reset, or physically disconnect/reconnect the device.
Surely for something like an external hard drive, powering it off properly is important to prevent data damage/loss. I know for certain that Windows does this.
Mergedinto: 689605
Status: Duplicate (was: Assigned)

Sign in to add a comment