From owner-freebsd-current@FreeBSD.ORG Wed Jan 21 10:43:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23EA616A4CE for ; Wed, 21 Jan 2004 10:43:13 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C1E643D3F for ; Wed, 21 Jan 2004 10:43:08 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E11E766CD1; Wed, 21 Jan 2004 10:43:07 -0800 (PST) Date: Wed, 21 Jan 2004 10:43:07 -0800 From: Kris Kennaway To: Ken Smith Message-ID: <20040121184307.GA41138@xor.obsecurity.org> References: <20040121182730.GB40652@xor.obsecurity.org> <20040121183959.GA25589@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <20040121183959.GA25589@electra.cse.Buffalo.EDU> User-Agent: Mutt/1.4.1i cc: "Robin P. Blanchard" cc: current@freebsd.org cc: Kris Kennaway Subject: Re: Strange behaviour X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 18:43:13 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 21, 2004 at 01:39:59PM -0500, Ken Smith wrote: > I have the same machine (Dell 2650) and it's getting locked up in > a very similar way, you don't need to get NFS involved to have > processes get locked uup in getblk. I'm slowly trying to remove > variables but so far it seems like network activity of some sort > helps cause the lockup. The easiest way to make it lock up was > doing backups through the network. But find's cranked up by the > nightly cron jobs can get locked in getblk as well (while there > are no NFS partitions mounted, but things like cvsup updates of > a local repo are happening). Once things start to get locked up > like this the system slowly degrades. I can usually ssh in and > reboot it if I catch it soon enough, if I leave it for a couple > of days it will seem like it's up (rwhod is running) but ssh-ing > in won't work. >=20 > sledge (amd64 machine in the cluster) was showing similar symptoms > this morning, it had failed doing its nightly rebuild/reboot and > things like mtree commands were wedged since a day or two ago. >=20 > The Dell I have here is not really in production at all, if me > doing anything here will help I'm game... OK, sounds like it might be something to do with vnode locking. Turning on DEBUG_VFS_LOCKS might help to find it. Kris --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADsg7Wry0BWjoQKURAqMfAKCopHtBEznVG114xdGjYlevsqAicACggbFb e0P6SE5QIHNOMnz44xGwI64= =2+nK -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI--