Date: Tue, 4 Feb 1997 13:50:05 -0800 (PST) From: Simon Shapiro <Shimon@i-Connect.Net> To: freebsd-bugs Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by Message-ID: <199702042150.NAA14678@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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: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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702042150.NAA14678>