From owner-freebsd-bugs  Fri Jan 31 18:00:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA28353
          for bugs-outgoing; Fri, 31 Jan 1997 18:00:03 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA28347;
          Fri, 31 Jan 1997 18:00:02 -0800 (PST)
Resent-Date: Fri, 31 Jan 1997 18:00:02 -0800 (PST)
Resent-Message-Id: <199702010200.SAA28347@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, shimon@i-connect.net
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28158
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 31 Jan 1997 17:55:00 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id SAA16247; Fri, 31 Jan 1997 18:54:38 -0800 (PST)
Message-Id: <199702010254.SAA16247@sendero.i-connect.net>
Date: Fri, 31 Jan 1997 18:54:38 -0800 (PST)
From: shimon@i-connect.net
Reply-To: shimon@i-connect.net
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn bytes for lncntp
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         2633
>Category:       bin
>Synopsis:       fsck -p in /etc/rc fails with cannot alloc nnnn bytes for lncntp
>Confidential:   yes
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 31 18:00:01 PST 1997
>Last-Modified:
>Originator:     Simon Shapiro
>Organization:
Atlas Telecom
>Release:        FreeBSD 2.2-BETA_A i386
>Environment:

	P6-200, 64MB RAM, 32GB disk on AHA-2940w

>Description:

	When booting, fsck -p (in /etc/rc) fails with ``cannot alloc nnnn bytes for
	lncntp''  error, thus makes it impossible to boot into init level 2.

	This happens consistently for file systems which are about 4GB large.
	Does not seem to happen on smaller ones.
	Reports for more sever behavior under SMP kernels.

>How-To-Repeat:

	Create a file system $GB or more in size
	Boot the system and enjoy.

>Fix:
	
	Workaround:  Comment out the fsck -p in /etc/rc and pray.

>Audit-Trail:
>Unformatted: