I have still vnodes problem in 4.8-stable with /sys/kern/vfs_subr.c
1.249.2.30.
Ishizuka-san, could you possibly try the following command line
repeatedly while slowdown is being observed?
% vmstat -m | grep '^ *vfscache'
If the third number of its output is approaching or
I have still vnodes problem in 4.8-stable with /sys/kern/vfs_subr.c
1.249.2.30.
(1) #1 machine (Celeron 466 with 256 mega byte rams)
% sysctl kern.maxvnodes
kern.maxvnodes: 17979
% sysctl vm.zone | grep VNODE
VNODE: 192,0, 18004,122,18004
This
On Mon, Jun 09, 2003, Masachika ISHIZUKA wrote:
I have still vnodes problem in 4.8-stable with /sys/kern/vfs_subr.c
1.249.2.30.
(1) #1 machine (Celeron 466 with 256 mega byte rams)
% sysctl kern.maxvnodes
kern.maxvnodes: 17979
% sysctl vm.zone | grep VNODE
VNODE:
I have still vnodes problem in 4.8-stable with /sys/kern/vfs_subr.c
1.249.2.30.
% sysctl kern.maxvnodes
kern.maxvnodes: 17979
% sysctl vm.zone | grep VNODE
VNODE: 192,0, 18004,122,18004
This looks pretty normal to me for a quiescent system.
I
On Mon, 25 May 2003, Mike Harding wrote:
I'm running a very recent RELENG-4 - but I had a suspicion that this was
unionfs related, so I unmounted the /usr/ports union mounts under a jail
in case this was causing the problem, and haven't seen the problem
since. It's possible I accidently
On Mon, 26 May 2003, Mike Harding wrote:
Er - are any changes made to RELENG_4_8 that aren't made to RELENG_4? I
thought it was the other way around - that 4_8 only got _some_ of the
changes to RELENG_4...
Ack, my fault ... sorry, wasn't thinking :( RELENG_4 is correct ... I
should have
Ack, only 512Meg of memory? :( k, now you are beyond me on this one ...
I'm running 4Gig on our server, with 2Gig allocated to kernel memory ...
only thing I can suggest is try slowly incrementing up your maxvnodes and
see if that helps, but, I'm not sure where your upper threshhold is with
I'm a little confused. What state is the vnlru kernel thread in? It
sounds like vnlru must be stuck.
Note that you can gdb the live kernel and get a stack backtrace of any
stuck process.
gdb -k /kernel.debug /dev/mem (or whatever)
proc N
I'll try this if I can tickle the bug again.
I may have just run out of freevnodes - I only have about 1-2000 free
right now. I was just surprised because I have never seen a reference
to tuning this sysctl.
- Mike H.
On Tue, 2003-05-27 at 11:09, Matthew Dillon wrote:
I'm a little
:I'll try this if I can tickle the bug again.
:
:I may have just run out of freevnodes - I only have about 1-2000 free
:right now. I was just surprised because I have never seen a reference
:to tuning this sysctl.
:
:- Mike H.
The vnode subsystem is *VERY* sensitive to running out of KVM,
10 matches
Mail list logo
