nfs4 mounting
Trond Myklebust
trond.myklebust at fys.uio.no
Tue Sep 25 12:46:51 EDT 2007
The Linux NFSv4 server has a somewhat messed up namespace. Whichever
partition is exported as 'fsid=0' is defined to be the root NFSv4
directory '/'. Anything which is not a subdirectory of that root
partition will never be seen by NFSv4.
Cheers
Trond
On Fri, 2007-09-21 at 17:11 -0400, Saurabh Sehgal wrote:
> Hi,
>
> hmm ... maybe that is what the problem is ... I actually upgrades one
> of our machines to SLES 10 ...
>
> uname -a
> Linux amdha03 2.6.16.46-0.4-smp #1 SMP Mon Apr 2 17:59:08 UTC 2007
> x86_64 x86_64 x86_64 GNU/Linux
>
> I saw the nfsd4 daemon start up. However, anything other than the /
> directory I cannot mount ( like you had previously suggested ) ...
> why is that .. how do I mount directories that are not / ...
>
> Plase let me know if there is anything else I need to do to mount
> non / directories .. I really appreciate your help !
>
> rgds,
>
> Saurabh
>
>
> On 9/21/07, Trond Myklebust <trond.myklebust at fys.uio.no> wrote:
> Oh... 2.6.5 Is that perhaps a SLES-9 kernel? I'm not sure they
> include
> support for NFSv4.
>
> Trond
>
>
> On Fri, 2007-09-21 at 16:43 -0400, Saurabh Sehgal wrote:
> > yes, I have also tried with -t nfs4 options, and I get the
> same error ...
> >
> > On 9/21/07, Trond Myklebust <trond.myklebust at fys.uio.no>
> wrote:
> > > On Fri, 2007-09-21 at 15:31 -0400, Saurabh Sehgal wrote:
> > > > Hi,
> > > >
> > > > I tried mounting with 192.168.23.101:/ ... I still get
> the same
> > > > error :
> > > > nfs warning: mount version newer than kernel ..
> > >
> > > There should only be one version of the NFSv4 binary mount
> protocol. Did
> > > you remember the '-t nfs4'?
> > >
> > > Trond
> > >
> > > > uname -a
> > > > Linux amdha02 2.6.5-7.283-smp #1 SMP Wed Nov 29 16:55:53
> UTC 2006
> > > > x86_64 x86_64 x86_64 GNU/Linux
> > > >
> > > > rgds,
> > > >
> > > > Saurabh
> > > >
> > > > On 9/21/07, Trond Myklebust <trond.myklebust at fys.uio.no>
> wrote:
> > > > On Fri, 2007-09-21 at 13:11 -0400, Saurabh
> Sehgal wrote:
> > > > > Hi,
> > > > >
> > > > > I am working on a project that makes use of
> nfs (v3) to
> > > > concurrently
> > > > > write to a file across a network of four
> machines ( to do
> > > > some record
> > > > > keeping ). Some tester on my team tried to
> mount nfs as :
> > > > >
> > > > > 192.168.23.101:/home /home nfs
> > > > > rw,hard,bg,intr,vers-v4,suid,tcp,timeo=600 0 0
> > > > >
> > > > >
> > > > > The vers field of this mount line
> in /etc/fstab is wrong,
> > > > but is
> > > > > ignored, and the mounting goes through.
> However, during the
> > > > concurrent
> > > > > reads/writes to the file, the file gets
> corrupted.
> > > > >
> > > > > Any suggestions, on why might this be
> happening ?, and what
> > > > really
> > > > > happens when the vers field of the line is
> specified as
> > > > such ? Any
> > > > > help is appreciated !
> > > >
> > > > Please read http://nfs.sourceforge.net/#faq_a8
> > > >
> > > > > Also, when I tried to mount nfs4 correctly by
> issuing
> > > > something like:
> > > > >
> > > > >
> > > > > mount -t nfs4 -o rw,hard,bg,intr
> 192.168.23.101:/home /home
> > > > >
> > > > > i get the following error :
> > > > > root at amdha02 :/root# mount -t nfs4 -o
> rw,hard,bg,intr
> > > > > 192.168.23.101:/home /ho >
> > > > > mount: wrong fs type, bad option, bad
> superblock on
> > > > > 192.168.23.101:/home,
> > > > > or too many mounted file systems
> > > >
> > > > Try mounting 192.168.23.101:/ instead
> of /home...
> > > >
> > > > Trond
> > > >
> > > >
> > >
> > >
>
>
More information about the NFSv4
mailing list