Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Dec 2008 22:09:23 +1100
From:      Peter Jeremy <peterjeremy@optushome.com.au>
To:        freebsd-current@freebsd.org
Subject:   Panic "rw lock not unlocked" doing NFS mount
Message-ID:  <20081228110923.GD64280@server.vk2pj.dyndns.org>

next in thread | raw e-mail | index | archive | help

--3Gf/FFewwPeBMqCJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I'm running -current from just before Christmas and when I tried to
NFS mount a ZFS filesystem, the server panic'd.  Backtrace is:
#9  0xffffffff802be55b in panic (fmt=3DVariable "fmt" is not available.) at=
 /usr/src/sys/kern/kern_shutdown.c:559
During symbol reading, unsupported tag: 'DW_TAG_volatile_type'.
#10 0xffffffff802bc8f1 in rw_destroy (rw=3D0xffffffff80a20fe0) at /usr/src/=
sys/kern/kern_rwlock.c:180
#11 0xffffffff80336636 in vfs_export (mp=3D0xffffff0001c6a000, argp=3D0xfff=
ffffe96b10960) at /usr/src/sys/kern/vfs_export.c:247
#12 0xffffffff8033de6f in vfs_donmount (td=3D0xffffff0001c8dab0, fsflags=3D=
0x11100, fsoptions=3D0xffffff0016c69700) at /usr/src/sys/kern/vfs_mount.c:9=
98
#13 0xffffffff8033eeec in nmount (td=3D0xffffff0001c8dab0, uap=3D0xfffffffe=
96b10c00) at /usr/src/sys/kern/vfs_mount.c:417
#14 0xffffffff8044d12d in syscall (frame=3D0xfffffffe96b10c90) at /usr/src/=
sys/amd64/amd64/trap.c:898
#15 0xffffffff8042fd4b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exce=
ption.S:338

I'm not sure why nmount(2) is being invoked on the NFS server.  Also, the
path passed into nmount() is not the path I was mounting (though it is a
path I tried unsuccessfully to mount yesterday).  Has anyone got any
suggestions?

Just before I sent this, I tried the mount again and got EPERM on the
client.  Since I'd been renaming ZFS mountpoints, I assumed that mountd
had gotten itself confused.  When I SIGHUP'd it, I got another identical
panic.

--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.

--3Gf/FFewwPeBMqCJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAklXXmMACgkQ/opHv/APuIeG6QCeOoWNC5/o1jrlfjYjGemRcI1I
slgAmgNfBrDa5ahQXII2fssXuhKwQAOf
=MyIL
-----END PGP SIGNATURE-----

--3Gf/FFewwPeBMqCJ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081228110923.GD64280>