From owner-freebsd-stable Tue Jan 23 12: 2:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id 0A1B937B401 for ; Tue, 23 Jan 2001 12:02:05 -0800 (PST) Received: (cpmta 14878 invoked from network); 23 Jan 2001 11:10:06 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.67) with SMTP; 23 Jan 2001 11:10:06 -0800 X-Sent: 23 Jan 2001 19:10:06 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id LAA00428; Tue, 23 Jan 2001 11:10:05 -0800 (PST) (envelope-from gharris) Date: Tue, 23 Jan 2001 11:10:05 -0800 From: Guy Harris To: Guy Harris , Neil Brown , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010123111005.D344@quadrajet.flashcom.com> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010123162930.B5443@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Tue, Jan 23, 2001 at 04:29:30PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 04:29:30PM +0100, Matthias Andree wrote: > Okay. So, as a conclusion, my original bug report boils down to: > > "You cannot mount read-only file systems with NFS v3 from a Linux 2.2.18 > server to a FreeBSD 4.2-STABLE client. Use NFS v2 instead." > > The question remains: Linux kernel problem or FreeBSD client problem? I'd consider the Linux kernel sending NFS3ERR_ROFS over the wire in the response to an ACCESS call checking write access to be an error on the part of the Linux NFS server, as 1) the spec doesn't list NFS3ERR_ROFS as a valid reply and 2) as per my other mail, it means it can't properly report what's permitted if the ACCESS call checks both read and write access - NFS3ERR_ROFS doesn't say "reading is OK, writing isn't" Presumably that's why the protocol spec doesn't list NFS3ERR_ROFS (Perhaps it would've been better had the V3 protocol specified that either 0 or an NFS3ERR_xxx value be supplied for each of the permission bits checked, although that raises the question of whether any server would, say, allow read access and allow write access but disallow simultaneous read/write access.) One might also consider it a FreeBSD client problem that it can't cope with this, if the Solaris client can, although that one might be a weaker claim (i.e., the Linux server is arguably violating the spec, whilst the FreeBSD client is merely apparently not doing as good a job of coping with servers violating the spec as the Solaris client is, in this case). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message