: > After replacing this disc, the speed issues are history.
:
: Thanks for the update. Closing.
:
: > The cpu burning is related to NFSv4, after reconfigured to use NFSv3
: > my file server is working smoothly.

Maybe a bit more detail... The faulty hd made the system behave like
without dma, so I was able to make cpu consumption up to 80-100 %
even without NFS.

But with NFSv4 the system totally slowed down.

: I'd be interested to learn more about what happened there so it can
: get fixed. Did I understand correctly that with a squeeze kernel
: NFSv4 writes do not increase nfsd CPU consumption very much, while
: with a wheezy kernel it provokes near 100% CPU consumption?

I don't really know, didn't benchmark the new wheezy system over NFS
with the squeeze kernel.

But occasionally on wheezy, multiple instances of nfsd seem to use
all of the cpu time, when configured as NFSv4. I can trigger it
anytime on my setup by transfering big files, any vdr recording will
do. They are usually 500MB..2TB in size.

: If you have time, I suppose I'd suggest filing a new bug with a
: summary of the problem.

I'm not surprised if there is already one, because someone in
#debian.fi@ircnet already told he had to use NFSv3 to get rid of his
problems - before I even upgraded to wheezy.

If I have the time, I might dig deeper.

--
Teemu



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120504081403.GA15361@tambu.hopto.org">http://lists.debian.org/20120504081403.GA15361@tambu.hopto.org