From owner-freebsd-bugs  Sat Nov 11 20:50: 9 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 8C33937B4D7
	for <freebsd-bugs@FreeBSD.org>; Sat, 11 Nov 2000 20:50:01 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id UAA69035;
	Sat, 11 Nov 2000 20:50:01 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 014C437B479; Sat, 11 Nov 2000 20:49:37 -0800 (PST)
Message-Id: <20001112044937.014C437B479@hub.freebsd.org>
Date: Sat, 11 Nov 2000 20:49:37 -0800 (PST)
From: lew@lppi.com
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-1.0
Subject: kern/22779: procfs corruption in FreeBSD 4.1.1-REL (ps gives "bad namelist")
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         22779
>Category:       kern
>Synopsis:       procfs corruption in FreeBSD 4.1.1-REL (ps gives "bad namelist")
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 11 20:50:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Lew Payne
>Release:        4.1.1-RELEASE
>Organization:
Lew Payne Publishing, Inc.
>Environment:
FreeBSD nfs1.techhosting.net 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE #0:
lewis@nfs1.techhosting.net:/usr/src/sys/compile/NFS  i386

>Description:
procfs seems to become corrupt over time.  This causes "ps" and "w" to fail with a "bad namelist" error.  Once this happens, it is impossible to manage processes.  Even re-genning the kernel, or booting good old kernel.GENERIC, does not fix this...  like managing the system with a blindfold on.  Can someone please, please help me with this.  I'm also running NFS (some machines as clients, some as servers) on the boxes, and the problem doesn't seem to discriminate between servers/clients.


  When it does, nothing fixes it... not even a reboot or re-genning the kernel.  Even booting with kernel.GENERIC won't fix the problem.
>How-To-Repeat:
Install 4.1.1-REL, and these ports, then just let it run for a week:
bzip2-1.0.1             jpeg-6b                 mysql-client-3.22.32
gdbm-1.8.0              libtool-1.3.4           mysql-server-3.22.32
gettext-0.10.35         lynx-2.8.3.1            rsync-2.4.6
gmake-3.79.1            mtr-0.42
or just write me for telnet access into my cluster.

>Fix:
Reinstalling FreeBSD from scratch temporarily solves the problem, but after several days of uptime, the problem resurfaces.  Please help!

>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message