From owner-freebsd-bugs  Tue Feb  4 13:50:06 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA14680
          for bugs-outgoing; Tue, 4 Feb 1997 13:50:06 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA14669;
          Tue, 4 Feb 1997 13:50:02 -0800 (PST)
Date: Tue, 4 Feb 1997 13:50:02 -0800 (PST)
Message-Id: <199702042150.NAA14669@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Simon Shapiro <Shimon@i-Connect.Net>
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Reply-To: Simon Shapiro <Shimon@i-Connect.Net>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/2633; it has been noted by GNATS.

From: Simon Shapiro <Shimon@i-Connect.Net>
To: (Satoshi Asami) <asami@vader.cs.berkeley.edu>
Cc: freebsd-gnats-submit@freefall.freebsd.org
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Date: Tue, 04 Feb 1997 14:37:15 -0800 (PST)

 Hi Satoshi Asami;  On 04-Feb-97 you wrote: 
 
 ...
 
 > I've seen this before, but not for 4GB disks.  More like 40GB.  I had
 > to raise the kernel data size limit (MAXDSIZ).
 
 This is the most dangerous parameter in the system!  Just grepping for
 it has froze the machine solid :-)  I need a serial console...
 
 It is set to 256MB.  Should be enough...
 
 Simon