On Sun, Sep 21, 2008 at 8:50 AM, Martin Knoblauch <knobi@xxxxxxxxxxxx> wrote: > ----- Original Message ---- > >> From: Chuck Lever <chucklever@xxxxxxxxx> >> To: Martin Knoblauch <knobi@xxxxxxxxxxxx> >> Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>; Greg Banks <gnb@xxxxxxxxxxxxxxxxx>; linux-nfs list <linux-nfs@xxxxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx; Peter zijlstra <a.p.zijlstra@xxxxxxxxx> >> Sent: Thursday, September 18, 2008 8:24:42 PM >> Subject: Re: [RFC][Resend] Make NFS-Client readahead tunable >> >> On Thu, Sep 18, 2008 at 6:53 AM, Martin Knoblauch wrote: >> > ----- Original Message ---- >> > >> >> From: Andrew Morton >> >> To: Martin Knoblauch >> >> Cc: Greg Banks ; linux-nfs list >> ; linux-kernel@xxxxxxxxxxxxxxx; Peter zijlstra >> >> >> Sent: Thursday, September 18, 2008 10:47:33 AM >> >> Subject: Re: [RFC][Resend] Make NFS-Client readahead tunable >> >> >> >> On Thu, 18 Sep 2008 01:38:57 -0700 (PDT) Martin Knoblauch >> >> wrote: >> >> >> >> > > No. mount(8) will pass unrecognised options straight down into the >> >> > > filesystem driver. >> >> > > >> >> > >> >> > Has that always been the case, or is it a recent change? I have to support >> >> RHEL4 userland, which is not really new. >> >> >> >> It's been that way for ever and ever. It's how all these guys: >> >> >> >> y:/usr/src/25> grep Opt_ fs/*/super.c|wc >> >> 781 2626 33703 >> >> >> >> get handled. >> > >> > while that seems to be not to complicated, I seem to have a problem passing >> the mount options to the kernel. They come down as mount data version "6". >> Apparently mount(8) or mount.nfs(8) are doing the parsing and send down the >> legacy data block. So, what is the minimum version of mount or mount.nfs that >> pass the options down unaltered? >> >> The mount command has passed a string of options to the kernel for >> particular file systems for a while, but the facility for the NFS >> client to parse a string of mount options in the kernel was added only >> recently -- at least 2.6.23 or 2.6.24 is required to support this. >> Before this, the mount command parsed these options. >> > > I understand that. Question remains, which version of the mount(8) or nfs.mount(8) command do I need to pass the options to the kernel. You can use the latest version of nfs-utils, which is 1.1.3 to get a version of mount.nfs that passes a string of mount options. You should probably also replace the mount command with the latest version from the util-linux package to get a version that starts the mount.nfs subcommand instead of trying to do an NFS mount itself. This is not needed for experimentation, though. You can issue mount.nfs directly. -- Chuck Lever -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
