From: Steve Dickson Subject: Re: NFS: unknown mount option: grpid Date: Thu, 10 Apr 2008 12:07:46 -0400 Message-ID: <47FE3B52.5060907@RedHat.com> References: <47FE0C42.6030900@TechFak.Uni-Bielefeld.DE> <56D1CF7A-BB26-4D07-B47D-9D43D55A1B8F@oracle.com> <47FE2C2D.1070703@redhat.com> <20080410153449.GA9429@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: NFS list , Linux NFSv4 mailing list , Jan Sanders To: "J. Bruce Fields" Return-path: In-Reply-To: <20080410153449.GA9429@fieldses.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org List-ID: J. Bruce Fields wrote: >>>>> The mount call returns with EINVAL invalis argument. >>>>> >>>>> From strace: >>>>> mount("nfs-server:/volumes/www", "/vol/www", "nfs", MS_NOSUID, >>>>> "grpid,addr=192.168.0.123") = -1 EINVAL (Invalid argument) >>>>> >> >> However, I was not aware of a requirement for NFS mount to ignore all >> options it doesn't understand. >> >> It's easy enough to add, I suppose. Community opinion? > > This is exactly what "-s" ("sloppy") is supposed to do, right? At > least, that's what "man mount" says. Not exactly... Looking at the code it seems '-s' will cause the mount.nfs command to ignore unknown _nfs_ options. In this case it appears the sys_mount call is failing which something different. steved.