Date: Wed, 21 Mar 2007 08:48:09 -0700 From: "Kevin Oberman" <oberman@es.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org Subject: Re: Curious behavior of HAL in 2.18 Message-ID: <20070321154809.2B80445047@ptavv.es.net> In-Reply-To: Your message of "Wed, 21 Mar 2007 02:26:41 EDT." <1174458401.79605.54.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1174492089_30122P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: Joe Marcus Clarke <marcus@marcuscom.com> > Date: Wed, 21 Mar 2007 02:26:41 -0400 > > > --=-OXpYbk/p7gFCiF1GWj94 > Content-Type: text/plain > Content-Transfer-Encoding: quoted-printable > > On Tue, 2007-03-20 at 21:08 -0700, Kevin Oberman wrote: > > > From: Joe Marcus Clarke <marcus@marcuscom.com> > > > Date: Tue, 20 Mar 2007 23:54:21 -0400 > > > > > > On Tue, 2007-03-20 at 15:10 -0700, Kevin Oberman wrote: > > > > Following up my own message, It is not the mounting or umounting of a > > > > system that triggers it. It is the creation or deletion of a device i> n > > > > /dev. > > > > > > > > I can understand this triggering HAL, but I don't know why it wants t> o > > > > alway remount all of the system partitions. > > > > > > Please provide a step-by-step procedure of what you're doing to create > > > this behavior as well as the version of FreeBSD. > > > > Only one step: > > mdconfig -f file > > or > > mdconfig -d -u 1 > > In stable, the first would have been "mdconfig -a -t vnode -f file". > > > > FreeBSD slan.es.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Mar 19 09:07:> 43 PDT > > > > A couple of seconds after I issue the command (which creates or deletes > > /dev/md1), I get the messages. > > > > All ports are current except p5-Cairo which won't build the new version. > > I just tried this on 7-CURRENT amd64 with up-to-date ports. I do not > see this behavior. What other HAL configuration have you done (e.g. > extra fdi files)? Can you try to isolate which process is trying to > mount these file systems (e.g. using ktrace or truss)? It is probably > happening via hald, but something is telling hald to do this. My guess > is gnome-volume-manager. > > Joe I don't think that this is relevant, but the file I was using as the backing store for the md device is about 2GB in size and is a valid ufs device. I have no idea what an fdi file is. The only hal configuration I have done is to hal-storage-fixed-mount-change-uid.privilege and hal-storage-fixed-mount.privilege where I have added myself the the Allow i.e."Allow=uid:oberman". Of course, my system is running i386, not amd64. Any place to read up on the gnome-volume-manager? I didn't see much in the FAQ. -- 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 --==_Exmh_1174492089_30122P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFGAVO5kn3rs5h7N1ERAggAAJ46FPqRCAtaayY0SYxTu/5Sx63+QgCdFKH2 XxmXSBxVnsluFlQSPPZSOJY= =SQuc -----END PGP SIGNATURE----- --==_Exmh_1174492089_30122P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070321154809.2B80445047>