Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote:
> Hi Suresh,
>
> On Tue, 2018-07-24 at 09:58 +0000, Suresh Jayaraman wrote:
>> Hi Trond et al,
>>
>> On 07/19/2018 12:39 PM, Aditya Agnihotri wrote:
>>> We are testing our pNFS server with linux client, when the server
>>> returns multiple paths to a v4 DS via GETDEVINFO, we see that the
>>> client validated the paths (does exchange id) but does not use the
>>> alternate paths in IO.
>>> Tracing the code path, it seems that when DS is a NFS v3 server,
>>> path is added, but for NFS v4 DS server, client setup function
>>> callback path fails to add.
>>
>> Is this observation that rpc_clnt_setup_test_and_add_xprt() doesn't
>> call
>> rpc_xprt_switch_add_xprt() neither in the test function nor let
>> rpc_clnt_add_xprt() add the xprt correct? This seems to be limiting
>> Linux pNFS client from using multiple paths with Tegile/WD pNFS
>> server.
>>
>> If yes, would you like a patch that attempts to fix this?
>
> I believe that the only reason why the NFSv4 DS server code was never
> changed is that it would need to be tested, and none of us has such a
> setup to test with.
>
> So yes, if you're able to test out that setup and are seeing a bug,
> then we're happy to take a fix.
>
Thanks Trond. It looks like we need to go through an approval process
before we submit the patch. I guess it shouldn’t take long.
Thanks,
--
Suresh Jayaraman��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
