I have a system that is being used as a high performance NFS server
FreeBSD nfs2 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Tue Jan 4
19:14:40 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS i386
Two CPUs (tried hyperthreading and not), 4 GB of memory
CPU: Intel(R) Xeon(TM) CPU 2.40GHz
M wrote:
I have a system that is being used as a high performance NFS server
FreeBSD nfs2 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Tue Jan 4
19:14:40 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS i386
Two CPUs (tried hyperthreading and not), 4 GB of memory
CPU: Intel(R) Xeon(TM)
Le 06/01/2005 à 10:01:54-0500, M a écrit
I have a system that is being used as a high performance NFS server
FreeBSD nfs2 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Tue Jan 4
19:14:40 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS i386
messages in /var/log/messages or on the
, Erik
Since i am going to set up a SMP NFS server too, i would be interested
if this really solves the OP's problem. After all, he is talking about a
hard lock with no messages.., as opposed to a kernel panic, which in
my understanding always produces messages.
Heinrich Rebehn
University of Bremen
On Thu, Jan 06, 2005 at 04:49:56PM +0100, Heinrich Rebehn wrote:
Since i am going to set up a SMP NFS server too, i would be interested
if this really solves the OP's problem. After all, he is talking about a
hard lock with no messages.., as opposed to a kernel panic, which in
my
