On 03/20/2014 10:12 AM, Steve Dickson wrote: > > > On 03/19/2014 03:41 PM, Trond Myklebust wrote: >> >> On Mar 19, 2014, at 14:22, Steve Dickson <SteveD@xxxxxxxxxx> wrote: >>> >>> What's going on is-ECONNREFUSED is being seen in call_connect_status() >>> and the task is not a soft connection. So call_timeout() is call which >>> eventual times out the mount… >> >> This is what is confusing me. I’d expect that the rpc_ping() would be the >> first thing to be sent on the wire by rpc_create(), and that ping >> should normally have the RPC_SOFTCONN flag set. >> >>> So just for fun I make the SETCLIENTID rpc soft, but for some >>> reason that didn't work either... I thought for sure it would... > I see you point... Using quick systemtap scripts it turns out > rpc_ping is not failing (returns 0x0) and it should because > the server is definitely down! Found it... The rpc_delay call in call_connect_status() is causing a callback to be scheduled and run before rpc_exit_task. Unfortunately that call back (__rpc_atrun) clears the status... I'll posting my version of the fix shortly.. steved. -- 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
