[Bug 13140] sometimes mounts both raw device and partition

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=13140
Ubuntu | hal


martin.pitt at ubuntu.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED
          Component|gnome-volume-manager        |hal
     Ever Confirmed|0                           |1
            Summary|usb-disk fail to mount      |sometimes mounts both raw
                   |automatically               |device and partition




------- Additional Comments From martin.pitt at ubuntu.com  2005-08-17 07:04 UTC -------
(In reply to comment #4)
> Sorry for the delay in reply. 
> 
> I've done sth. not so smart since the bug report -- I repartitioned the
> usb-disk, and now I can not re-produce the bug even though now I still have a
> sda1 partition.

Ok, since it now works for you I strongly feel that you suffered from the same
problem as in #13520.

> The current behavior is a little strange too though. Once I plug in the
> usb-disk, both /dev/sda and /dev/sda1 got mounted and two icons are created on
> desktop.

This is not intended, but sometimes happens if the boot sector and/or first
blocks still have a valid VFAT signature. This happens if you first format
/dev/sda, and then repartition and use /dev/hda1. I will try to add a check to
hal to not let this happen, and I will devote this bug report for it.

> If I trying to unmount the /dev/sda disk (right click on the desktop
> icon), the sda1 icon also disapears. Is that the intended behavior?

In principle yes, if a device has multiple partitions, all of them are unmounted
at the same time since the device is ejected. The unintended part is that
/dev/sda gets mounted in the first place.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.