From owner-freebsd-current Sun Oct 13 13:57: 0 2002 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 E5B7D37B401 for ; Sun, 13 Oct 2002 13:56:58 -0700 (PDT) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A65443E97 for ; Sun, 13 Oct 2002 13:56:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0126.cvx40-bradley.dialup.earthlink.net ([216.244.42.126] helo=mindspring.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 180pn2-000098-00; Sun, 13 Oct 2002 13:56:45 -0700 Message-ID: <3DA9DDC5.1547947E@mindspring.com> Date: Sun, 13 Oct 2002 13:55:33 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: current@FreeBSD.org Subject: Re: current unable to exec processes under load References: <20021012213213.GC93425@xor.obsecurity.org> <20021013195623.GA33370@tara.freenix.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ollivier Robert wrote: > According to Kris Kennaway: > > load: 0.00 cmd: tcsh 8403 [inode] 0.01u 0.00s 0% 1076k > > The dreaded "inode" problem. I've been seeing this from time to time where the > system will be blocked for all I/O on a given disk with all processes waiting > on "inode". > > Generally updating the system to a more recent "fixes" the problem till next > time. I don't know where it comes from :-( It's actually the name for "vp->v_vnlock" from FFS; specifically, line #1231 of /usr/src/sys/ufs/ffs/ffs_vfsops.c. It's actually the address of the vp->v_lock. Acquisition supposedly times out in 50ms. You may want to try compiling with: options DEBUG_LOCKS It's locked and unlocked in /usr/src/sys/kern/vfs_default.c in vop_stdlock(), vop_stdunlock() (which should also be instrumented for DEBUG_LOCKS, but isn't), vop_sharedlock(), and (sort of) in vop_nolock(). So try the option, if that doesn't work, instrument vop_stdlock() and try it again, and if that still gives no information, check with whoever wrote the code. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message