From owner-freebsd-bugs Mon Feb 3 22:50:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA22507 for bugs-outgoing; Mon, 3 Feb 1997 22:50:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA22501; Mon, 3 Feb 1997 22:50:02 -0800 (PST) Date: Mon, 3 Feb 1997 22:50:02 -0800 (PST) Message-Id: <199702040650.WAA22501@freefall.freebsd.org> To: freebsd-bugs Cc: From: Simon Shapiro Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by Reply-To: Simon Shapiro 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 To: (Joerg Wunsch) Cc: FreeBSD-gnats-submit@freebsd.org, (J Wunsch) 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