Date: Sat, 23 Jun 2007 08:24:06 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: freebsd-current@freebsd.org Subject: NFS problems with recent -current Message-ID: <20070622222406.GG24720@turion.vk2pj.dyndns.org>
next in thread | raw e-mail | index | archive | help
--Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have 7.0-CURRENT/i386 from 7th June running as an NFS server with a 6-STABLE/amd64 client and the server is regularly getting flooded with the following: Jun 23 04:00:45 server kernel: uma_zalloc_arg: zone "mbuf" with the followi= ng non-sleepable locks held: Jun 23 04:00:45 server kernel: exclusive sleep mutex nfsd_mtx r =3D 0 (0xc0= 7ec040) locked @ /usr/src/sys/nfsserver/nfs_srvsock.c:660 Jun 23 04:00:45 server kernel: KDB: stack backtrace: Jun 23 04:00:45 server kernel: db_trace_self_wrapper(c071c52b,d630ab10,c058= 5bcf,c071c8af,d630ab24,...) at db_trace_self_wrapper+0x26 Jun 23 04:00:45 server kernel: kdb_backtrace(c071c8af,d630ab24,4,1,0,...) a= t kdb_backtrace+0x29 Jun 23 04:00:45 server kernel: witness_warn(5,0,c073093c,c0721815,d630ab34,= =2E..) at witness_warn+0x1bf Jun 23 04:00:45 server kernel: uma_zalloc_arg(c1044000,d630ab88,2,8,c3147d2= 4,...) at uma_zalloc_arg+0x34 Jun 23 04:00:45 server kernel: nfs_realign(c07ec040,0,c072c0f7,294,0,...) a= t nfs_realign+0x6f Jun 23 04:00:45 server kernel: nfsrv_rcv(c3103dec,c3147d00,2,168,0,...) at = nfsrv_rcv+0x49a Jun 23 04:00:45 server kernel: nfssvc(c3fa1c00,d630acfc,8,c,c075df08,...) a= t nfssvc+0x77f Jun 23 04:00:45 server kernel: syscall(d630ad38) at syscall+0x29a Jun 23 04:00:45 server kernel: Xint0x80_syscall() at Xint0x80_syscall+0x20 Jun 23 04:00:45 server kernel: --- syscall (155, FreeBSD ELF32, nfssvc), ei= p =3D 0x280c9d17, esp =3D 0xbfbfe8bc, ebp =3D 0xbfbfe8d8 --- The server seems to run for some time and then start generating these errors. I seem to be able to stop them by unmounting the client and restarting the NFS server processes (though once the server deadlocked). So far, I've got records of it starting: Jun 11 or Jun 12 (I've lost the first error in this block) Jun 15 22:15:01 Jun 21 22:36:00 Jun 22 22:59:56 I'm not sure what the underlying trigger is - I'm not around at those times (though I do leave mutt running on the client). The times don't match any periodic jobs I've got running and don't match fetchmail/sendmail activity on the server. Has anyone else seen this or have any ideas where to look? --=20 Peter Jeremy --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGfEwG/opHv/APuIcRAo83AJ9pL0JrcXBi56pSO4OtW4vv7UKB1ACfRghA +fNYZXEvLq0hNZSbPRJqp3I= =gVe2 -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070622222406.GG24720>