Re: [7.0.2] problems with spinlock under FreeBSD?

okay, I just doubled my FDs to 8192 from 4136 and will watch things
... anyone know of a way of telling how many are currently in use, and
where they peaked? somethign similar to 'netstat -m' showing mbufs?

thanks tom ...

On Thu, 24 Aug 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > you still have your account on that machine if you want to take a quick
> > look around ... else, anything else I should be looking at?
>
> I poked around and couldn't learn much of anything --- the logfiles from
> yesterday are already gone, apparently. I did find some interesting
> entries in today's logfiles:
>
> %grep Lru *
> 5432.61820:FATAL 1: ReleaseLruFile: No open files available to be closed
> postmaster.5437.36290:FATAL 1: ReleaseLruFile: No open files available to be closed
> postmaster.5437.62218:FATAL 1: ReleaseLruFile: No open files available to be closed
>
> What we see here are backends choking because there are no free kernel
> file descriptor slots, even after they've closed *all* of their own
> discretionary FDs. So you've definitely got a serious problem with
> insufficient FD slots. Time to tweak those kernel parameters.
>
> I still don't see a linkage between too few FDs and the stuck-spinlock
> crashes, but maybe there is one.
>
> regards, tom lane
>

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org