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 12, 2011, at 1:49 PM, Jim Rees wrote:

> The question for us is how long should an nfsroot client wait for the server
> to reply.  It sounds like the client used to wait longer than it does now.

Before, the client performed the GETPORT(NFS) step synchronously, first.  This took 30 seconds or so to timeout.  When it did, the client decided to proceed with port 2049.  Then it went on to do the other mount tasks, and at the point had waited long enough that these tasks did not time out while waiting for the switch port.

> It seems to me the client should wait at least 90 seconds so that the
> situation you're in (servers on non-portfast ports) will work.  I would
> think they should wait indefinitely, since there's not much else they can
> do.

It should be simple to wrap the (MNT(mnt), NFS(getroot)) steps in a while(true) loop.  Would mount_root_nfs() be the right place for this?

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