Kris Kennaway wrote:
[snip]
See discussion on stable@ for what is believed to be the problem.
Backing out the changes to vfs_lookup.c would work around the problem
for now (although it reintroduces other bugs).
Hi,
since i am being bitten by the same bug, i would like to try that out. I
am
On Wed, May 24, 2006 at 03:15:42PM +0200, Marko Lerota wrote:
> Nash Nipples <[EMAIL PROTECTED]> writes:
>
> >Hi Marko,
> >
> > Actually i dont find that load critical. I think those lines well tell that
> > actually the process is running 581m42s and now it utilizes 13.48%
>
> Sometimes it
Nash Nipples <[EMAIL PROTECTED]> writes:
>Hi Marko,
>
> Actually i dont find that load critical. I think those lines well tell that
> actually the process is running 581m42s and now it utilizes 13.48%
Sometimes it was 80%
> which sounds like a "kernel tuning issue" if you have excluded nfs
Hi Marko,
Actually i dont find that load critical. I think those lines well tell that
actually the process is running 581m42s and now it utilizes 13.48% of available
WCPU which is a long run and hopefully successfull if no nfs failures took
place.
Im pretty confident that FreeBSD wont let a
Marko Lerota <[EMAIL PROTECTED]> writes:
> PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND
> 429 root 1 40 1204K 820K - 0 581:42 13.48% nfsd
> 430 root 1 40 1204K 820K - 0 10:37 0.00% nfsd
>
> Here is the config
> rc.con
My nfs server is chewing to much CPU even when nobody writes
to nfs partition. The clients are RHES4. I don't know much about
nfs but I followed the steps in handbook. Look:
last pid: 43588; load averages: 0.46, 0.77, 0.81
28 processes: 1 running, 27 sleeping
CPU states: 0.0% user, 0.0% n
