Date: Sun, 30 Jan 2000 07:47:44 -0800 From: "Jay Krell" <jay.krell@cornell.edu> To: <questions@freebsd.org> Subject: Re: "too many files open"? Message-ID: <002001bf6b39$5a3146f0$8101a8c0@jayk-home4nt>
next in thread | raw e-mail | index | archive | help
I tried reinstally BSD 3.4 clean to a 34gig drive, with BSD taking the
entire drive (but keeping a partition table so I get the BootMgr so I might
boot other drives). The kernel paniced while running sysinstall. I believe I
reproed this twice. So I moved the contents of the 2gig fat to this 34gig
drive (using DOS) and reinstalled BSD to the ~27gig drive, this time with no
leading 2gig fat, and the partitioning like so:
100meg /
100meg swap
100meg /var
~27 meg /usr
same as the defaults, but bumping up the sizes on the first three (from like
50, 37, 20).
boot into BSD, don't rebuild world, kernel, ports, or anything, just mount
the other drive, untar "dist.tar" (~gig of /usr/ports/distfiles) cd
/usr/ports/dev*/codec* ; make clean
after a while it printed
/usr/ports/dev*/codec*/work/JX*/ACE/ACE_wrappers/ace/OS.i:
cc1plus in free: warning: recursive call
cc1plus in malloc: warning: recursive call
then
panic: vm_object_deallocate: object deallocated too many times: 0
reboot
cd /usr/ports/dev*/codec*
make clean
make
Still very slow, but it hasn't crashed and it has gotten further. It had
been on JXApplication.cc for many minutes though, so I control-c, make, it's
again sitting on that file. I started building Gwydion Dylan on other
console to see if the additional "stress" will repro the panic..
No one has seen anything like this?
- Jay
-----Original Message-----
From: Jay Krell <jay.krell@cornell.edu>
To: questions@freebsd.org <questions@freebsd.org>
Date: Saturday, January 29, 2000 8:29 PM
Subject: Re: "too many files open"?
>Well.. the network on this machine is incompletely configured, but Samba is
>installed. I found that there were lots of nmbd processes running. I
>commented out the appro lines in inetd.conf. This might explain the "too
>many open files".
>
>Building Code Crusader (and Gwydion Dylan 2.x) still takes hours -- more
>than eight running them concurrently. I'm reinstalling with a seperate
>100meg /var (I coulldn't cd /var ; mv * /usr/var) and will link /tmp to
>/usr/tmp..
>
>If this still doesn't work, I'll find another home for the 2gig fat and go
>closer to a "dangerously dedicated" hard drive..
>
> ..Jay
>
>-----Original Message-----
>From: Jay Krell <jay.krell@cornell.edu>
>To: questions@freebsd.org <questions@freebsd.org>
>Date: Saturday, January 29, 2000 2:48 AM
>Subject: "too many files open"?
>
>
>>Has anyone seen a BSD ~3.4 install where
>>
>>1) building /usr/ports/devel/codecrusader is amazingly slow
>> The system is a 450MHz Pentium II with 128megs; I didn't
>> notice this on a 200MHz Pentium Pro with 128megs
>>2) trying to do something like concurrently build codecrusader
>> and the kernel (or maybe it was only make depend on the kernel)
>> produces the error "too many open files" upon which basically
>> nothing works (until a reboot) -- running top reports that
>> /usr/lib/termmap.so.2 doesn't exist, running ls reports "too many
>> open files in system", and so does ps, dmesg
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002001bf6b39$5a3146f0$8101a8c0>