Date: Sun, 21 Feb 2010 15:19:17 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Kevin Oberman <oberman@es.net> Cc: gnome@freebsd.org Subject: Re: Problems with gnome-mount and UFS volumes Message-ID: <1266783557.98965.72.camel@shumai.marcuscom.com> In-Reply-To: <20100221174257.D02E91CC0E@ptavv.es.net> References: <20100221174257.D02E91CC0E@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-KPXk3ioRIL6wt2POCXIL Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable 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 > >=20 > > 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 > > > >=20 > > > > 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 w= ould 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. > > > > >=20 > > > > > Is there a reasonable way to prevent this from happening? I'd rea= lly like > > > > > t be able to unplug this disk when I shut down the VirtualBox con= tainer. > > > > >=20 > > > > > Running the latest versions of all of the gnome ports and hald. > > > > >=20 > > > > > 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. > > > >=20 > > > > How is the device remounted? That is, when the device gets remount= ed, > > > > what does the output of mount(8) look like? > > >=20 > > > Here is the sequence of events I see: > > >=20 > > > 1. Plug in disk > > > 2. HAL reports the error "org.freedesktop.Hal.UnknownError. An unknow= n > > > error occurred" I get two pop-ups with this, si I assume it is fai= ling > > > 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-u= pdates) > > > 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) > > >=20 > > > The only difference is the '_' added to the mount point as the prior > > > mount point was not deleted when the disk was unmounted.=20 > > >=20 > > > 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/u= fs > > > name due to the fact that it is the 'd' partition of the slice. > >=20 > > Use the attached script to watch devd events when you insert, mount, an= d > > unmount this volume. Post the results. >=20 > Filtered out all of the CREATE and DESTROY messages from apm0. > Plugged in the drive: > !system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev=3Dufs/WindowsVB > !system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev=3Dufsid/4aa5767251674= 1c2d > !system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev=3Dufs/WindowsVBd > !system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cdev=3Dufs/WindowsVB > !system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cdev=3Dda0s1d > !system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cdev=3Dufs/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. > gnome-mount 0.8 > ** (gnome-mount:8739): DEBUG: Unmounting /org/freedesktop/Hal/devices/vol= ume_label_WindowsVB > ** (gnome-mount:8739): DEBUG: Setting up 750ms timer for Flushing Cache d= ialog > ** (gnome-mount:8739): DEBUG: in unmount_done : user_data =3D 0x0 > ** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_label_= WindowsVB: org.freedesktop.Hal.Device.UnknownError : An unknown error occur= ed >=20 > Exit 1 > !system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev=3Dda0s1d > !system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev=3Dufs/WindowsVB > !system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cdev=3Dda0s1d > 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/vol= ume_label_WindowsVB > ** (gnome-mount:8764): DEBUG: Setting up 750ms timer for Flushing Cache d= ialog > ** (gnome-mount:8764): DEBUG: in unmount_done : user_data =3D 0x0 > ** Message: Unmount failed for /org/freedesktop/Hal/devices/volume_label_= WindowsVB: org.freedesktop.Hal.Device.UnknownError : An unknown error occur= ed >=20 > Exit 1 > !system=3DDEVFS subsystem=3DCDEV type=3DCREATE cdev=3Dda0s1d > !system=3DDEVFS subsystem=3DCDEV type=3DDESTROY cdev=3Dda0s1d > 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. >=20 > Oddly, I can't use the Unmount menu option to unmount today. I have no > idea why. It sends out: > Unable to unmount WindowsVB__ >=20 > umount: unmount of /media/WindowsVB__ failed:=20 > Operation not permitted >=20 > 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. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-KPXk3ioRIL6wt2POCXIL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkuBlUQACgkQb2iPiv4Uz4egtQCgmX8W9iuyGO7gt042XGr9/9rY 0fIAnjbNKUXs4+asMAOp00JRenlvsL4i =lxKR -----END PGP SIGNATURE----- --=-KPXk3ioRIL6wt2POCXIL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1266783557.98965.72.camel>