Bug 8233

Summary: umount of one file system causes other systems to be unmounted too
Product: Mageia Reporter: Marc Krämer <mageia>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal    
Version: 2   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: nautilus-3.4.1-1.mga2.src.rpm CVE:
Status comment:

Description Marc Krämer 2012-11-28 14:42:32 CET
I have an internal sata-dvd drive. having mounted this dvd and an external usb disk.
If I unmount the dvd disk via tray eject, the usb drive is unmounted too.

In log I can see udisksd is cleaning up both mount points, but states only one device was unmounted by a user (Unmounted /dev/sr0 on behalf of uid 500)

The same issue occurs if you have more than one usb disk on the same usb hub. On unmount of one device on this hub, all disks are unmounted. This is really annoying!

I'm not sure if this is related, but more information may help, so:
on attaching the usb disk to one of the ports I get the following messages (but this was not the case with this error):

Nov 26 01:23:25 localhost kernel: [373150.489534] usb 1-1.1: new high-speed USB device number 9 using ehci_hcd
Nov 26 01:23:26 localhost kernel: [373150.566169] ehci_hcd 0000:00:1a.0: fatal error
Nov 26 01:23:26 localhost kernel: [373150.570057] ehci_hcd 0000:00:1a.0: HC died; cleaning up
Nov 26 01:23:26 localhost kernel: [373150.572893] ehci_hcd 0000:00:1a.0: force halt; handshake ffffc900117ac024 00004000 00004000 -> -110
Nov 26 01:23:26 localhost kernel: [373150.572897] ehci_hcd 0000:00:1a.0: HC died; cleaning up
Nov 26 01:23:26 localhost kernel: [373150.576932] usb 1-1.1: device descriptor read/all, error -108
Nov 26 01:23:26 localhost kernel: [373150.576939] hub 1-1:1.0: cannot disable port 1 (err = -19)
Nov 26 01:23:26 localhost kernel: [373150.576955] hub 1-1:1.0: cannot reset port 1 (err = -19)
Comment 1 Manuel Hiebel 2013-10-22 12:19:39 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 2 Manuel Hiebel 2013-11-23 16:16:03 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD