Referral in NFSv4

Juilee Hapse juilee.hapse at gmail.com
Fri Jun 1 07:58:11 EDT 2007


Hi,

  Of the things you asked...
1. Can you do a normal v4 mount of dfswin1:/vicepa?
 --> yes this can be done.

 2. firewall issue.
--> firewall is disabled on all 3 m/cs ( 2 servers and one client)

 3. Network trace.
--> Have taken one through wireshark. Attaching that file.

 4. Versions of client and server:
---> server is 2.6.18 (both the servers)
---> client 2.6.20

Also attaching the logs for  client/server output of :
#tail -f /var/log/messages


Thanks,
Juilee


On 5/30/07, Fredric Isaman <iisaman at citi.umich.edu> wrote:
>
>
>
> On Wed, 30 May 2007, Juilee Hapse wrote:
>
> > Ya thats done.
> > #mount
> > /export/foo on /export/foo type none (rw,bind)
> >
> > I think the problem might be on the dfswin1 server.
> > /vicepa is mounted and exported.
> >
> > #cat /etc/exports
> > /vicepa
> > *(rw,nohide,insecure,no_subtree_check,sync,anonuid=65534,anongid=65534)
> >
> > #df -k
> > /dev/sda6              1686728     32844   1653884   2% /vicepa
> >
> > Anything missing here?
> >
> > Thanks,
> > Juilee
> >
> >
>
> Can you do a normal v4 mount of dfswin1:/vicepa?  If so, apart from
> filewall issues, that should not be the problem.
>
> The next question is what does the network trace look like?  Is
> NFS4ERR_MOVED being sent when you try to access <SERVER>:/foo? If the
> answer is yes, then is the correct referral being sent over the wire? (If
> you can't tell, you can send me the network trace.)
>
> Also, what kernel versions are you using on the client and servers?
>
>         Fred
>
>
>
>
>
> > On 5/30/07, Fredric Isaman <iisaman at citi.umich.edu> wrote:
> >>
> >> On Wed, 30 May 2007, Juilee Hapse wrote:
> >>
> >> > Hi,
> >> >
> >> > I am trying to make referral work in nfsv4. But no luck. So I put
> debugs
> >> > statements in the nfs-utils code(fsloc.c).
> >> >
> >> > I access a directory under my pseudo-root. This directory is the
> access
> >> > point for referral.
> >> >
> >> > #cat /etc/exports
> >> >
> >> > /export
> >> >
> >>
> *(rw,fsid=0,insecure,no_subtree_check,sync,anonuid=65534,anongid=65534,nohide)
> >> > /export/etc
> >> >
> *(rw,insecure,no_subtree_check,sync,anonuid=65534,anongid=65534,nohide)
> >> >
> /export/foo  *(insecure,no_subtree_check,nohide,refer=/vicepa at dfswin1)
> >> >
> >>
> >> One obvious potential source of error.../export/foo must be a
> mountpoint.
> >> In other words, is it listed when you type 'mount'?  If not, you can
> >> mount --bind it to itself.
> >>
> >>         Fred
> >>
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/nfsv4/attachments/20070601/2e59b4bf/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: network_trace
Type: application/octet-stream
Size: 3528117 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20070601/2e59b4bf/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfsv4_server.log
Type: application/octet-stream
Size: 67129 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20070601/2e59b4bf/attachment-0001.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfsv4_client.log
Type: application/octet-stream
Size: 111482 bytes
Desc: not available
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20070601/2e59b4bf/attachment-0002.obj 


More information about the NFSv4 mailing list