Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
To:     linux-nfs <linux-nfs@vger.kernel.org>
From:   guy keren <guy@vastdata.com>
Subject: nfs4.1 and nconnect - is this supported?
Message-ID: <9d726e22-8c47-41ac-727b-3a27a9919fc6@vastdata.com>
Date:   Thu, 15 Jul 2021 16:16:19 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Precedence: bulk


hi,

i wonder if the linux client's nfs nconnect feature was designed to 
support NFS4.1 (or higher) versions? according to our experimentation, 
the linux client seems to just alternate messages between the multiple 
RPC/TCP connections, and does not seem to adhere to the NFS 4.1 protocol 
requirement, that when using multiple connections, the client needs to 
use BIND_CONN_TO_SESSION when trying to user a 2nd connection with the 
same NFS4.1 session.

was this done on purpose? or is this configuration not supported by 
linux client's 'nconnect'? or am i missing something?

thanks,
--guy