From owner-freebsd-questions  Fri Apr 14 17:14:23 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id RAA19068
          for questions-outgoing; Fri, 14 Apr 1995 17:14:23 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA18760
          ; Fri, 14 Apr 1995 17:09:38 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id RAA18059; Fri, 14 Apr 1995 17:08:51 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id RAA00358; Fri, 14 Apr 1995 17:08:51 -0700
Message-Id: <199504150008.RAA00358@corbin.Root.COM>
To: Network Coordinator <nc@ain.charm.net>
cc: freebsd-hackers@FreeBSD.org, freebsd-questions@FreeBSD.org
Subject: Re: Proceses that won't die - follow up 
In-reply-to: Your message of "Thu, 13 Apr 95 20:16:59 EDT."
             <Pine.BSF.3.91.950413201459.7619A-100000@ain.charm.net> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 14 Apr 1995 17:08:49 -0700
Sender: questions-owner@FreeBSD.org
Precedence: bulk

>
>For some reason at the same time the system decides to not kill any 
>processes (except shells) the system won't allow an ls -l of the / 
>directory. If one tries /bin/ls /, there is no problem, but for the -long 
>information, it just STOPS. In fact very few proceses that do any sort of 
>file i/o (cp, find, etc) seem to be working very well. I haven't seen, or 
>have reason to believe that the filesystem has errors on it.
>
>Any ideas would be appreciated.

   I believe this is known bug which has been fixed in the 4/12 snapshot.

-DG