Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1477

Summary: New problem with linux nfsd and BSDI nfs client
Product: [Retired] Red Hat Linux Reporter: kresa
Component: nfs-serverAssignee: Jeff Johnson <jbj>
Severity: medium Docs Contact:
Priority: low    
Version: 5.2CC: kresa
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-06-03 14:08:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description kresa 1999-03-11 00:58:42 UTC
There seems to be a problem with nfsd in
nfs-server-2.2beta37  (the one included in RedHat 5.2)

here are the exports from Linux:

/tmp/try-export *,insecure)

*** note the 'insecure'

you then mount it from BSDI (3.1 or 4.0)

and try to write to a file there (under the mount point).

the file gets created with size 0

no matter what you do.

the following message is logged on the linux


Mar 11 01:06:42 fury nfsd[280]: strange write req from co
unt 1717856768 len 5

(fury is the linux box, amos-04 is the BSDI)

additional facts:

1. when writing from BSDI to any other OS we have here

   everything is fine.

2. this problem is *not occuring* when you try to

   write from any other OS (Sun0S 4, Solaris, IRIX)

   to linux

3. the problem doesn't exist neither in

   the older nfs-server-2.2beta29

   (shipped in RedHat 5.1) nor in the new

   nfsd from linux-nfs-0.4.22 based on

   knfsd (kernel 2.2.x level nfsd support)

There seems to be a new condition

in nfsd.c (in 2.2beta37):

492:    if (count > NFS_MAXDATA || count >
argp->data.data_len) {
493:            Dprintf(L_NOTICE,
494:                    "strange write req from %s: count
%lu len %lu",
495:                    nfsclient->clnt_name, count,
496:            return NFSERR_IO;
497:    }

which BSDI nfs client obviously doesn't satisfy.

(i'm posting this also to the relevant mailing-list,

 please  post any suggestions on



CS System Group
Hebrew University of Jerusalem

Comment 1 Jeff Johnson 1999-03-24 23:51:59 UTC
Does this bug persist with the knfsd running on a 2.2 kernel?

Please reopen this bug if so.