reclaimer hang
Harry Edmon
harry at atmos.washington.edu
Thu Nov 15 14:37:08 EST 2007
Trond Myklebust wrote:
> On Thu, 2007-11-15 at 10:17 -0800, Harry Edmon wrote:
>
>> Trond Myklebust wrote:
>>
>>> On Thu, 2007-11-15 at 10:08 -0800, Harry Edmon wrote:
>>>
>>>
>>>
>>>> 2. Yes, I know that is a strange IP number, but that is what is in the
>>>> log file. What I sent you was cut out of the kernel log on the server.
>>>>
>>>>
>>> OK. What happens if you use the 'clientaddr=' mount option with the
>>> correct IP address that the server should use to call back your client?
>>>
>>> Trond
>>>
>>>
>> There is more than one client for this server. So are you talking about
>> all the clients? Since I am doing the mounts via automount, this would
>> be difficult. Does it have to be the multi-homed clients only?
>>
>
> You should _definitely_ do it for multi-homed clients. Pretty much
> anything for which 'getent hosts $(hostname)' returns a wrong IP
> address.
>
>
>> Finally, the man page for nfs on my etch system says:
>>
>> clientaddr=n On a multi-homed client, this causes the client to
>> use a
>> specific callback address when communicating with
>> an NFS
>> version 4 server. This option is currently ignored.
>>
>> Do I need a more recent version of mount?
>>
>
> Nope. Only a more recent manpage :-)
>
> Trond
>
I tried "getent hosts `hostname`" on some of my single-homed systems,
and I notice they are returning "127.0.0.1" since that is what is in the
/etc/hosts file (a Debian artifact). Would that cause a problem? By
the way, none of them return 1.129.255.255.
More information about the NFSv4
mailing list