Date: Fri, 30 Aug 2002 16:23:21 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Arnvid Karstad <arnvid@karstad.org>, <bmah@FreeBSD.ORG>, <freebsd-stable@FreeBSD.ORG> Subject: Re: Problems with FreeBSD - causing zalloc to return 0 ?! Message-ID: <20020830162006.J14642-100000@mail1.hub.org> In-Reply-To: <200208301904.g7UJ4vc8017053@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Is there any definite way of determining this? From what I can find int he man page, VNODES have to do with the file system and directory lists ... my last two crashes look to be related to the file system itself, so have started to watch the VNODE numbers to, but is there some way of determining what I should raise, and where? I'm running 4Gig of RAM and Dual CPU over here, so having a swap device large enough to 'dump core' is kinda out of the question, so I can't provide any more infomration that i have so far in other messages :( And, also, should any 'server class' operating system be more graceful about such things? Some sort of soft limit that triggers it to refuse new processes or something when its hit, so that it doesn't actually crash? Kinda like the NMBCLUSTERS warning/error message when its set too low? On Fri, 30 Aug 2002, Matthew Dillon wrote: > Hmm. It looks to me that the kernel may be running out of KVM > resources. There are a couple of possibilities here. Arnvid, > if possible I would like to download your vmcore (the one you were > using in all the debug output filed in the PR) and associated > kernel.debug and investigate this here. > > Please note that vmcore's may contain sensitive information such as > passwords and such, so it's entirely up to you/your-company to decide > whether to do this or not. If you decide that it is OK to supply the > core to me for examination please put it up somewhere where I can download > it (via ftp or the web), in a place normally hidden from view, and send > me a PRIVATE email that does not Cc: the FreeBSD mailing list with > the URL where it can be found. > > -Matt > Matthew Dillon > <dillon@backplane.com> > > > :On Fri, 30 Aug 2002 09:52:02 -0700 - "Bruce A. Mah" <bmah@FreeBSD.ORG> wrote: > :> Just a wild guess: vm_zone.c revision 1.30.2.5 was committed on 12 > :> August. Any chance that this might be relevant to your problem? > :> This is quite perplexing because almost all of the changes between 4.6 > :> and today's-head-of-RELENG_4_6 were in userland...the kernels should be > :> almost identical. > : > :Just for an intresting side note.... > : > :With option INVARIANTS we get no problems and vmstat's shows new highs' > : > :root@irc:/usr# vmstat -z | grep VNODE > :VNODE: 192, 0, 170782, 90, 170782 > : > :With out.. it dies horribly when the number reaches around 44000-45000. > : > :Arnvid > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020830162006.J14642-100000>