From owner-freebsd-current Sun Jan 27 16:52:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id EB54537B402 for ; Sun, 27 Jan 2002 16:52:15 -0800 (PST) Received: from teabag.demon.co.uk ([193.237.4.110] helo=teabag.cbhnet) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 16V01u-000Fop-0X for freebsd-current@freebsd.org; Mon, 28 Jan 2002 00:52:14 +0000 Received: from localhost (localhost [127.0.0.1]) by teabag.cbhnet (Postfix) with ESMTP id A092C64FF7 for ; Mon, 28 Jan 2002 00:52:13 +0000 (GMT) Date: Mon, 28 Jan 2002 00:52:13 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teabag.cbhnet To: freebsd-current@freebsd.org Subject: Re: Processes hanging in ``inode' state In-Reply-To: <20020126024324.A73968@dragon.nuxi.com> Message-ID: <20020128005040.S8421-100000@teabag.cbhnet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sat, 26 Jan 2002, David O'Brien wrote: > On Fri, Jan 25, 2002 at 03:51:08PM -0800, Jos Backus wrote: > > Recent -current on my system at work exhibits processes getting stuck in the > > ``inode'' state, causing the system to become unusable and requiring a reboot. > > > > I have been seeing this for about a week now; anyone else? > > I have been living with this in -CURRENT since mid-summer. I am lucky to > have 1 week uptimes. > > What editor are you using? I lock up my system most often using > mutt+vim. Similarly I've had numerous problems (probably going back around six months) with trn + vi. I thought it was just me... Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message