Date: Sun, 21 Feb 2010 12:56:06 -0800 From: "Kevin Oberman" <oberman@es.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org Subject: Re: Problems with gnome-mount and UFS volumes Message-ID: <20100221205606.088571CC0E@ptavv.es.net> In-Reply-To: Your message of "Sun, 21 Feb 2010 15:19:17 EST." <1266783557.98965.72.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Joe Marcus Clarke <marcus@marcuscom.com> > Date: Sun, 21 Feb 2010 15:19:17 -0500 > > On Sun, 2010-02-21 at 09:42 -0800, Kevin Oberman wrote: > > > From: Joe Marcus Clarke <marcus@marcuscom.com> > > > Date: Sat, 20 Feb 2010 13:57:52 -0500 > > > > > > On Tue, 2010-02-16 at 09:36 -0800, Kevin Oberman wrote: > > > > > From: Joe Marcus Clarke <marcus@marcuscom.com> > > > > > Date: Tue, 16 Feb 2010 02:04:02 -0500 > > > > > > > > > > On Mon, 2010-02-08 at 15:56 -0800, Kevin Oberman wrote: > > > > > > I use a UFS formatted USB disk for my VirtualBox container. When I plug > > > > > > it in, gnome-mount mounts it fine, but I can never unmount it. It > > > > > > unmounts fine, but remounts again immediately. No errors (and I would not > > > > > > expect any). I remember when this was a problem for MSDOSFS disks, but > > > > > > some magic was done to prevent this. It does not seem to work for UFS, > > > > > > though. > > > > > > > > > > > > Is there a reasonable way to prevent this from happening? I'd really like > > > > > > t be able to unplug this disk when I shut down the VirtualBox container. > > > > > > > > > > > > Running the latest versions of all of the gnome ports and hald. > > > > > > > > > > > > I would normally attach lshal output, but, since everything runs cleanly > > > > > > and without error, I don't know that it is needed. If so, let me know. > > > > > > > > > > How is the device remounted? That is, when the device gets remounted, > > > > > what does the output of mount(8) look like? > > > > > > > > Here is the sequence of events I see: > > > > > > > > 1. Plug in disk > > > > 2. HAL reports the error "org.freedesktop.Hal.UnknownError. An unknown > > > > error occurred" I get two pop-ups with this, si I assume it is failing > > > > twice. > > > > 2a. The device is mounted. (I assume this is a problem with trying to > > > > mount the multiple different instances of the device in /dev, /dev/ufs, > > > > and /dev/ufsid). > > > > 3. mount(8) shows: > > > > /dev/ufs/WindowsVBd on /media/WindowsVB (ufs, local,nosuid, soft-updates) > > > > 4. Request umount of device > > > > 5. Device unmounts correctly > > > > 6. Device immediately re-mounts as in 2 and 2a, including errors > > > > 7. mount now shows: > > > > /dev/ufs/WindowsVBd on /media/WindowsVB_ (ufs, local, nosuid, soft-updates) > > > > > > > > The only difference is the '_' added to the mount point as the prior > > > > mount point was not deleted when the disk was unmounted. > > > > > > > > The things I wonder about is confusion due to the three /dev entries, > > > > two of which start with '/dev/ufs' and the 'd' appended to the /dev/ufs > > > > name due to the fact that it is the 'd' partition of the slice. > > > > > > Use the attached script to watch devd events when you insert, mount, and > > > unmount this volume. Post the results. > > > > Filtered out all of the CREATE and DESTROY messages from apm0. > > Plugged in the drive: > > !system=DEVFS subsystem=CDEV type=CREATE cdev=ufs/WindowsVB > > !system=DEVFS subsystem=CDEV type=CREATE cdev=ufsid/4aa57672516741c2d > > !system=DEVFS subsystem=CDEV type=CREATE cdev=ufs/WindowsVBd > > !system=DEVFS subsystem=CDEV type=DESTROY cdev=ufs/WindowsVB > > !system=DEVFS subsystem=CDEV type=DESTROY cdev=da0s1d > > !system=DEVFS subsystem=CDEV type=DESTROY cdev=ufs/WindowsVBd > > Drive now mounted as: > > /dev/ufsid/4aa57672516741c2d 37838604 22514286 12297230 65% /media/WindowsVB > > > gnome-mount -u --block --verbose -d /dev/ufsid/4aa57672516741c2d > > Don't mount the ufsid node. I specifically added code to hal to ignore > those devices since they tend to mess things up. If you're going to > mount something manually, mount /dev/ufs/WindowsVBd. > > However, I thought the problem was with Nautilus and auto-mounting. It is. Perhaps you missed the '-u' in the gnome-mount command. This was the unmount operation. I used the CLI command due to nautilus, for some odd reason, giving me a permission failure while the command line did not. The partition was auto-mounted by nautilus. The is the ufsid device was mounted. I, too, thought that this should not happen, but... > > gnome-mount 0.8 > > ** (gnome-mount:8739): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_label_WindowsVB > > ** (gnome-mount:8739): DEBUG: Setting up 750ms timer for Flushing Cache dialog > > ** (gnome-mount:8739): DEBUG: in unmount_done : user_data = 0x0 > > ** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_label_WindowsVB: org.freedesktop.Hal.Device.UnknownError : An unknown error occured > > > > Exit 1 > > !system=DEVFS subsystem=CDEV type=CREATE cdev=da0s1d > > !system=DEVFS subsystem=CDEV type=CREATE cdev=ufs/WindowsVB > > !system=DEVFS subsystem=CDEV type=DESTROY cdev=da0s1d > > Drive now mounted as: > > /dev/ufs/WindowsVB 37838604 22514286 12297230 65% /media/WindowsVB_ > > > gnome-mount -u --block --verbose -d /dev/ufs/WindowsVB > > gnome-mount 0.8 > > ** (gnome-mount:8764): DEBUG: Unmounting /org/freedesktop/Hal/devices/volume_label_WindowsVB > > ** (gnome-mount:8764): DEBUG: Setting up 750ms timer for Flushing Cache dialog > > ** (gnome-mount:8764): DEBUG: in unmount_done : user_data = 0x0 > > ** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_label_WindowsVB: org.freedesktop.Hal.Device.UnknownError : An unknown error occured > > > > Exit 1 > > !system=DEVFS subsystem=CDEV type=CREATE cdev=da0s1d > > !system=DEVFS subsystem=CDEV type=DESTROY cdev=da0s1d > > Drive now mounted as: > > /dev/ufs/WindowsVB 37838604 22514286 12297230 65% > > /media/WindowsVB__ > > Yeah, this would be consistent with trying to mount the ufsid node. > That label is dynamic. If you mount the drive by another label (or the > physical device node), the ufsid label disappears. When you unmount, it > comes back. This confuses hal. OK. But it is mounting the ufsid device. This was an auto-mount. > > > > Oddly, I can't use the Unmount menu option to unmount today. I have no > > idea why. It sends out: > > Unable to unmount WindowsVB__ > > > > umount: unmount of /media/WindowsVB__ failed: > > Operation not permitted > > > > This is different from the normal case where I was receiving the "An > > unknown error occured". I don't know what might be causing this behavior > > change or why the CLI invocation of gnome-mount "works" while the menu > > one does nothing. > > It could be that something is using the mounted volume. If that is the case, why does the CLI command always work? I'm confused. (And, please note that this is not something I have seen before today. The nautilus 'Unmount' menu item has always worked before today. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100221205606.088571CC0E>