HAL taking over

[Kevin Oberman]

> From: Joe Marcus Clarke <marcus at marcuscom.com>
> Date: Fri, 03 Nov 2006 14:04:12 -0500
> 
> On Fri, 2006-11-03 at 10:54 -0800, Kevin Oberman wrote:
> > > From: Joe Marcus Clarke <marcus at marcuscom.com>
> > > Date: Thu, 02 Nov 2006 23:29:29 -0500
> > > 
> > > On Thu, 2006-11-02 at 19:53 -0800, Kevin Oberman wrote:
> > > > 
> > > > The partition that did not show a label looks fine when I do a dumpfs>  on
> > > > it, so the tunefs did the trick.
> > > 
> > > You need to restart hald, and re-login to GNOME for this to take effect> .
> > > lshal should show a volume.label property with your label.  If it does
> > > not, then gnome-vfs will not show a name.
> > 
> > But I did and it does! I logged out of Gnome and restarted all three
> > daemons in order dbus, polkitd, and hald. Then I restarted Gnome.
> 
> You might want to make sure gnome-vfs-daemon actually died, and was
> respawned.  If not, it will hold on to the old volume name.

I also tried rebooting the system. (It's my laptop, so it got rebooted
this morning when I got to work.) No improvement.
> 
> > 
> > udi = '/org/freedesktop/Hal/devices/volume_label_aux'
> >   volume.mount.valid_options = {'ro', 'noexec'} (string list)
> >   org.freedesktop.Hal.Device.Volume.method_execpaths = {'hal-storage-mo> unt', 'hal-system-storage-unmount', 'hal-system-storage-eject'} (string lis> t)
> >   org.freedesktop.Hal.Device.Volume.method_signatures = {'ssas', 'as', > 'as'} (string list)
> >   org.freedesktop.Hal.Device.Volume.method_names = {'Mount', 'Unmount',>  'Eject'} (string list)
> >   info.interfaces = {'org.freedesktop.Hal.Device.Volume'} (string list)
> >   block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_N> T02T53258CW'  (string)
> >   info.product = 'aux'  (string)
> >   info.udi = '/org/freedesktop/Hal/devices/volume_label_aux'  (string)
> >   block.is_volume = true  (bool)
> >   volume.mount_point = ''  (string)
> >   volume.is_mounted_read_only = false  (bool)
> >   volume.is_mounted = false  (bool)
> >   volume.num_blocks = 1048576  (0x100000)  (uint64)
> >   volume.size = 536870912  (0x20000000)  (uint64)
> >   volume.block_size = 512  (0x200)  (uint64)
> >   volume.uuid = ''  (string)
> >   volume.label = 'aux'  (string)
> >   volume.fsversion = '2'  (string)
> >   volume.fstype = 'ufs'  (string)
> >   volume.fsusage = 'filesystem'  (string)
> >   volume.ignore = false  (bool)
> >   volume.is_partition = false  (bool)
> >   volume.is_disc = false  (bool)
> >   block.minor = 97  (0x61)  (int)
> >   block.major = 0  (0x0)  (int)
> >   block.device = '/dev/ad2s1a'  (string)
> >   info.category = 'volume'  (string)
> >   info.bus = 'block'  (string)
> >   info.capabilities = {'block', 'volume'} (string list)
> >   info.parent =
> > '/org/freedesktop/Hal/devices/volume_part1_size_39999504384'  (string)
> 
> On what mount point will this volume be mounted?  At this point, it's
> not mounted at all.

Oh, yes, it is. It is mounted and I am able to edit files on it. But I
did another lshal and hald does not seem to know it. It still shows an
empty mount_point and both is_mounted_read_only and is_mounted are
false.

Something is clearly broken at this point.

Another thing I just noticed: I have a vnode backed md device mounted on
the system and it is not showing up at all. While I can believe that
gnome-vfs and hald don't understand md devices, but could the fact that
the backing file for the md volume is on the problem disk be related to
the problem?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 224 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20061103/397f1457/attachment.pgp