From owner-freebsd-questions Mon Jan 29 4:37:11 2001 Delivered-To: freebsd-questions@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 1C53837B402 for ; Mon, 29 Jan 2001 04:36:51 -0800 (PST) Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0TCaYe23867; Mon, 29 Jan 2001 13:36:34 +0100 (MET) Received: from localhost (pfeifer@localhost) by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0TCaXR34048; Mon, 29 Jan 2001 13:36:35 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: taygeta.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Mon, 29 Jan 2001 13:36:33 +0100 (CET) From: Gerald Pfeifer To: Cc: Subject: NFSv3 problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We recently switched a couple of 4.2-RELEASE boxes from NFSv2/UDP to NFSv3/TCP (which is the default now). NFS server is a Solaris 2.6 box with sufficient memory and horse power for our use. However, whenever the server has heavy IO (CPU states: 20.8% kernel, 79.2% iowait) due to backups etc., we are seeing errors like the following when accessing the NFS server (for a compile job): nfs server vexpert:/files3: not responding nfs server vexpert:/files3: is alive again (after fractions of a second) nfs server vexpert:/files3: not responding plan.o: Interrupted system call /var/tmp/cck28604.s: Assembler messages: /var/tmp/cck28604.s:205327: FATAL: Can't write plan.o: Interrupted system call or ... disk fill (when in fact, it is not). These failures are strictly confined to FreeBSD clients with NFSv3 (either TCP or UDP). FreeBSD clients with NFSv2/UDP do not experience this, nor do Solaris clients. So, this seems to be a FreeBSD bug. What shall we do? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message