[callbacks] server not responding...

[Daniel J Blueman]

On 10/07/07, Trond Myklebust <trond.myklebust at fys.uio.no> wrote:
> On Tue, 2007-07-10 at 16:55 +0100, Daniel J Blueman wrote:
> > I'm consistently seeing this message on an (ia32) NFSv4 server running
> > mainline 2.6.22 and previous kernels, with 2.6.20/22 ia32 and x86-64
> > clients:
> >
> > nfs4_cb: server 127.0.1.1 not responding, timed out
>                   ^^^^^^^^^
>
> > As I understand it, when a client mounts the server, the server tests
> > callback connections and tries to connect back to the client, however
> > I'm not seeing any TCP SYN packet go from server->client at mount
> > time.
> >
> > Where am I going wrong to check when and how callbacks are working?
> >
> > My /etc/exports is:
> >
> > /store  192.168.0.1/24(rw,fsid=0,async,insecure,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)
>
> You probably want to use the clientaddr mount option in order to tell
> the NFS client on which address the callback server is listening. (man 5
> nfs).

Thanks Trond, that resolved it!

On my multi-homed clients, I have only one interface up and loopback,
so could there not be logic at the client end to send the right
address that the server should use for callbacks, rather than
127.0.1.1 being given?

I couldn't see anything obvious in fs/nfs/callback*.c, but I'm not
familiar with it.

Thanks,
  Daniel
-- 
Daniel J Blueman