From owner-freebsd-hackers  Tue Apr  8 06:04:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA07642
          for hackers-outgoing; Tue, 8 Apr 1997 06:04:14 -0700 (PDT)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA07635
          for <hackers@freebsd.org>; Tue, 8 Apr 1997 06:04:10 -0700 (PDT)
Received: from dbws.etinc.com (db@dbws.etinc.com [204.141.95.130]) by etinc.com (8.8.3/8.6.9) with SMTP id JAA10842; Tue, 8 Apr 1997 09:09:33 -0400 (EDT)
Message-Id: <3.0.32.19970408090228.00694a84@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 08 Apr 1997 09:02:36 -0400
To: dg@root.com
From: dennis <dennis@etinc.com>
Subject: Re: 2.2.1R NFS and FTP load problem - More Info 
Cc: hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 04:39 PM 4/7/97 -0700, David Greenman wrote:
>>At 08:51 PM 4/7/97 +0200, you wrote:
>>>On Sat, Apr 05, 1997 at 01:32:09PM -0700, Terry Lambert wrote:
>>>> > >That's odd.. I had no problems installing 2.2R or 2.2.1R over NFS
>>with an
>>>> > >old ISA-only 486 with 8MB of RAM. 
>>>> > 
>>>> > Since there seems to be widespread doubt about this conclusion,
>>>> > if someone can get me a boot disk with some diagnostics for
>>>> > memory usage I'd be more than happy to try to track this down (as
>>>> > its no doubt going to bite me in the future)....theres a limited amount
>>>> > of info that I can gather with the install disk unfortunatly.....
>>
>>Well, the machine with 8 meg of RAM seems to work OK when I do a 
>>full developer load (sources), but fails on the "kernel developer"
>>selection. Could there be a bug there? Its a total pig when loading
>>the ports.....the throughput drops to like 5Kb and the disk sounds like
>>a choo-choo.....
>
>   The ports tree is escentially a few thousand directories, and the blocks
>for those are written out to disk syncronously (although the filesystem is
>mounted async).
>   I don't know why you're seeing a failure. Perhaps you could try doing a
>"ps" in the "emergency holographic shell"?

The system completely hangs...so theres no chance to check anything (kbd 
locks, pings to the machine fail, etc.......


Dennis