From owner-freebsd-fs Thu Mar 20 12:53:23 2003 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50A0837B401 for ; Thu, 20 Mar 2003 12:53:22 -0800 (PST) Received: from filer.fsl.cs.sunysb.edu (filer.fsl.cs.sunysb.edu [130.245.126.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E081D43F3F for ; Thu, 20 Mar 2003 12:53:19 -0800 (PST) (envelope-from ezk@fsl.cs.sunysb.edu) Received: from agora.fsl.cs.sunysb.edu (IDENT:Gf8K6Nw2kMQ/AqItNfCqfYxCIkR42BVW@agora.fsl.cs.sunysb.edu [130.245.126.12]) by filer.fsl.cs.sunysb.edu (8.12.5/8.12.8) with ESMTP id h2KKqush008641; Thu, 20 Mar 2003 15:52:56 -0500 Received: from agora.fsl.cs.sunysb.edu (IDENT:x/0dvmeQW1g4BZyCeNE+gEICLjU0klcw@localhost.localdomain [127.0.0.1]) by agora.fsl.cs.sunysb.edu (8.12.8/8.12.8) with ESMTP id h2KKqwb9019148; Thu, 20 Mar 2003 15:52:58 -0500 Received: (from ezk@localhost) by agora.fsl.cs.sunysb.edu (8.12.8/8.12.8/Submit) id h2KKqwTf019144; Thu, 20 Mar 2003 15:52:58 -0500 Date: Thu, 20 Mar 2003 15:52:58 -0500 Message-Id: <200303202052.h2KKqwTf019144@agora.fsl.cs.sunysb.edu> From: Erez Zadok To: freebsd-fs@FreeBSD.ORG Subject: cannot append on 5.0-RELEASE w/ NFSv2 Cc: X-MailKey: Erez Zadok Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm not sure if this is already known, but I came across what I think is an NFSv2 client-side bug in 5.0-RELEASE. My NFS server is Linux red hat 8.0 w/ latest errata kernel, w/ export options "rw,async". When my fbsd5 box mounts with -o nfsv2, the following /bin/sh (and /bin/bash) append command fails with "Permission Denied": echo foo >> bar when "bar" is NFS mounted from the linux server. I remounted the server w/ nfsv3 (took out the -o nfsv2 option) and appending works well. I didn't try -current or other NFS servers. Cheers, Erez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message