From shimon@sendero.i-connect.net  Fri Jan 31 17:55:02 1997
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
Subject: fsck -p in /etc/rc fails with cannot alloc nnnn bytes for lncntp
X-Send-Pr-Version: 3.2

>Number:         2633
>Category:       bin
>Synopsis:       fsck -p in /etc/rc fails with cannot alloc nnnn bytes for lncntp
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 31 18:00:01 PST 1997
>Closed-Date:    Tue Jun 2 18:02:07 PDT 1998
>Last-Modified:  Tue Jun  2 18:04:02 PDT 1998
>Originator:     Simon Shapiro
>Release:        FreeBSD 2.2-BETA_A i386
>Organization:
Atlas Telecom
>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.

>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: shimon@i-Connect.Net
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn bytes for lncntp
Date: Sat, 1 Feb 1997 14:13:09 +0100

 As shimon@i-Connect.Net wrote:
 
 > 	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 the error go away if you enable swapping before?
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
State-Changed-From-To: open->open 
State-Changed-By: fenner 
State-Changed-When: Sun Feb 2 10:08:36 PST 1997 
State-Changed-Why:  
It didn't.  darn that edit-pr anyway. 

From: Simon Shapiro <Shimon@i-Connect.Net>
To: (Joerg Wunsch) <joerg_wunsch@uriah.heep.sax.de>
Cc: FreeBSD-gnats-submit@freebsd.org, (J Wunsch) <j@uriah.heep.sax.de>
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Date: Mon, 03 Feb 1997 11:37:31 -0800 (PST)

 Hi J Wunsch;  On 01-Feb-97 you wrote: 
 > As shimon@i-Connect.Net wrote:
 > 
 > >     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 the error go away if you enable swapping before?
 
 I did not try.  Being that this is a standard /etc/rc, and the machine has
 64MB of RAM, it should not have a problem.  I think.
 
 Simon
 
 P.S.  I will try.
 
 Simon

From: Simon Shapiro <Shimon@i-Connect.Net>
To: (Joerg Wunsch) <joerg_wunsch@uriah.heep.sax.de>
Cc: FreeBSD-gnats-submit@freebsd.org, (J Wunsch) <j@uriah.heep.sax.de>
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Date: Mon, 03 Feb 1997 11:40:49 -0800 (PST)

 Hi J Wunsch;  On 01-Feb-97 you wrote: 
 > As shimon@i-Connect.Net wrote:
 > 
 > >     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 the error go away if you enable swapping before?
 
 If you look in /etc/rc, you will see that swap -a runs before the fsck.
 I do use ccdconfig and have /etc/ccd.conf file.  These may be related.
 
 Simon

From: j@uriah.heep.sax.de (J Wunsch)
To: Shimon@i-Connect.Net (Simon Shapiro)
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Date: Mon, 3 Feb 1997 22:15:02 +0100

 As Simon Shapiro wrote:
 
 > > Does the error go away if you enable swapping before?
 > 
 > If you look in /etc/rc, you will see that swap -a runs before the fsck.
 
 You'd like to say, i should *really* have looked before? :-)
 
 On another chance, does fsck simply run out of VM limits?  See
 ulimit...
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)

From: Simon Shapiro <Shimon@i-Connect.Net>
To: (Joerg Wunsch) <joerg_wunsch@uriah.heep.sax.de>
Cc: FreeBSD-gnats-submit@freebsd.org, (J Wunsch) <j@uriah.heep.sax.de>
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Date: Mon, 03 Feb 1997 23:32:26 -0800 (PST)

 Hi J Wunsch;  On 03-Feb-97 you wrote: 
 > As Simon Shapiro wrote:
 > 
 > > > Does the error go away if you enable swapping before?
 > > 
 > > If you look in /etc/rc, you will see that swap -a runs before the fsck.
 > 
 > You'd like to say, i should *really* have looked before? :-)
 > 
 > On another chance, does fsck simply run out of VM limits?  See
 > ulimit...
 
 Ulimit is ``unlimited'', unless it does something different (and silly?)
 at boot time.
 
 As this one is a basic, boot time, plain vanilla issue, I am sort of
 ``playing dumb'' here.  As I am still new here, am I expected to fix that
 (since I spoke first :-) or there is an ``official maintainer'' for this
 piece?
 
 Simon

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

  *  > >     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.
 
 I've seen this before, but not for 4GB disks.  More like 40GB.  I had
 to raise the kernel data size limit (MAXDSIZ).
 
  *  > Does the error go away if you enable swapping before?
  *  
  *  If you look in /etc/rc, you will see that swap -a runs before the fsck.
  *  I do use ccdconfig and have /etc/ccd.conf file.  These may be related.
 
 You are most likely running out of swap space, although it's hard to
 believe with 64MB of RAM.  How much swap do you have?
 
 Satoshi

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

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:02:04 -0800 (PST)

 Hi Satoshi Asami;  On 04-Feb-97 you wrote: 
 >  *  > >     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.
 > 
 > I've seen this before, but not for 4GB disks.  More like 40GB.  I had
 > to raise the kernel data size limit (MAXDSIZ).
 > 
 >  *  > Does the error go away if you enable swapping before?
 >  *  
 >  *  If you look in /etc/rc, you will see that swap -a runs before the
 fsck.
 >  *  I do use ccdconfig and have /etc/ccd.conf file.  These may be related.
 > 
 > You are most likely running out of swap space, although it's hard to
 > believe with 64MB of RAM.  How much swap do you have?
 > 
 > Satoshi
 
 128MB.  All this at boot time, from /etc/rc.  I doubt I am running out of
 swap space at that point.  especially when NOTHING else runs out of swap
 space later.  If the filesystem is anything less than 4GB, it works fine.
 Have you considered looking at the fact that fsck may be doing lseek or
 some other computation, based on the SIZE of the partition in bytes,
 encountering an integer overflow, or sign extention problem and trying to
 malloc (for example) a negative number, or a very small one, etc.
 
 Do we have llseek(2) in FreeBSD?
 
 Simon
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Tue Jun 2 18:02:07 PDT 1998 
State-Changed-Why:  
The originator says that after tweaking some parameters in login.conf 
the problem seems to have gone away. 
>Unformatted:
