From owner-freebsd-stable Tue Jan 23 15:29: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from subnet.sub.net (subnet.sub.net [212.227.14.21]) by hub.freebsd.org (Postfix) with ESMTP id 8889D37B69F for ; Tue, 23 Jan 2001 15:28:51 -0800 (PST) Received: from lyxys.ka.sub.org (uucp@localhost) by subnet.sub.net (8.8.8/8.8.8/1.2subnet-linux) with bsmtp id AAA28366; Wed, 24 Jan 2001 00:28:45 +0100 Received: from localhost (1832 bytes) by lyxys.ka.sub.org via sendmail with P:stdio/R:smart_host/T:inet_uusmtp (sender: ) (ident using unix) id for ; Tue, 23 Jan 2001 23:41:54 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Aug-23) Message-Id: From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export In-Reply-To: "from Bjoern Groenvall at Jan 23, 2001 05:26:54 pm" To: Bjoern Groenvall Date: Tue, 23 Jan 2001 23:41:54 +0100 (CET) Cc: FreeBSD Stable , Linux NFS mailing list , Guy Harris , Neil Brown , matthias.andree@stud.uni-dortmund.de X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matthias> The question remains: Linux kernel problem or FreeBSD client > Matthias> problem? > Or perhaps we should blame RFC1813? I don't think so, because .. > However, 1813 says that ACCESS > should return one of the following errors > NFS3ERR_IO > NFS3ERR_STALE > NFS3ERR_BADHANDLE > NFS3ERR_SERVERFAULT > ,and "The client encodes the > set of permissions that are to be checked in a bit mask. > The server checks the permissions encoded in the bit mask. > A status of NFS3_OK is returned along with a bit mask > encoded with the permissions that the client is allowed.". The wording here is totally clear: The client is not allowed write access on a read-only filesystem, so return NFS3_OK with the write bits turned off. > It also says > "NFS3ERR_ROFS > Read-only file system. A modifying operation was > attempted on a read-only file system." As ACCESS is not a "modifying operation", there is no contradiction here. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message