Re: [BUG?] Maybe NFS bug since 2.6.37 on SPARC64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Nov 3, 2011, at 5:11 PM, Jim Rees wrote:

> Trond Myklebust wrote:
> 
>> [ 442.666622] NFS: failed to create MNT RPC client, status=-60
>> [ 442.666732] NFS: unable to mount server 137.226.167.241, error -60
>> [ 442.666868] VFS: Unable to mount root fs via NFS, trying floppy.
>> [ 442.667032] VFS: Insert root floppy and press ENTER
>> 
>  Error 60 is ETIMEDOUT on SPARC, so it seems that the problem is
>  basically the same one that you see in your 2.6.32 trace (rpcbind:
>  server 137.226.167.241 not responding, timed out) except that now it is
>  a fatal error.
> 
>  Any idea why the first RPC calls might be failing here? A switch
>  misconfiguration or something like that perhaps?
> 
> Wasn't there a change in the way nfs mount options are handled by the kernel
> for nfsroot about the time of 2.6.39?  Something about changing from default
> udp to tcp maybe?

There was a change, but it was changed back to UDP because of problems like this.  Behavior in 3.0 or the latest 2.6.39 stable kernel may be improved.

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com




--
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


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux