Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp2707138ybx; Fri, 8 Nov 2019 08:13:26 -0800 (PST) X-Google-Smtp-Source: APXvYqwdA4eKFnck1cfkICAeqv5v7tmg/gs3i6lcpCOJthEh5h81rs0DPBtaG0fCaZd2G/6181Mw X-Received: by 2002:aa7:cd52:: with SMTP id v18mr11123612edw.280.1573229606303; Fri, 08 Nov 2019 08:13:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573229606; cv=none; d=google.com; s=arc-20160816; b=qRSYa56EczagFIGR3oXUcSW20ZyU5UFRuyEBArr5mEVVwJjdZqVqgpQcDuMOPYxJ71 SeUAZO00GHO0P6j6CQOmGGPQPEo3ZSXsOHTMJVxudV0qVj3By2ucfkgxZjzetvHSuEhe Y0Fm4tQQ/FBt2D4zTvx6JME+XOCV0fbjoCHMrxpR/ILDEH46OLdhGJCyg7i7rOJUBci/ mmXejq0eOCZpNAEb46vbIF2ISOstK0MbcxQ1BBjtXS2QJoXGmOm9AE9EhYFh4BX8pw9A QV5WcFEB3m5C2XnvE5+k9nRKIqcAY0KO9eKiZv+auVvjz81G1HhE9txuiS+QwfGcoO2D ql5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=GgR8SbJM/LwWNsFT9KWb1wzEtiup6uUwZwyMnR0ES20=; b=mM61HUOZbsUQVRrbH3Ph01YcuwmQ9n8Q669L2Iw/HjUMG2O+0YA3IihORL5ZxRvVTh Y4H9gyOLdDO8zE/+KyM9tw7rJwEawS9B+4qpevfFCqB9ZGDiQLMgqxA/UdruJpjkyDwW ZrL4auy38iFovBgqi+UqYMmtL7Fjly1J40SdpPklnINjGmvbV/9TlCjw7LkC5dSRE5MX 6CnWpHVNu3zvUlTlDxDzWOtIsG7gzXKqS3O2pZTxXNBP/TXGrrTejfNR0EQvJPkkQq48 mmuWWSI0wf7gVic0WQvFctFUhQe5Kr5/CFgH+bDLawzNlNbRqYgduKUYSK2ApC5UQE4+ 9tgg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@umich.edu header.s=google-2016-06-03 header.b=A6HKo7SE; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=umich.edu Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u18si4227699ejk.105.2019.11.08.08.12.52; Fri, 08 Nov 2019 08:13:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@umich.edu header.s=google-2016-06-03 header.b=A6HKo7SE; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=umich.edu Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727598AbfKHQJZ (ORCPT + 99 others); Fri, 8 Nov 2019 11:09:25 -0500 Received: from mail-vs1-f47.google.com ([209.85.217.47]:46021 "EHLO mail-vs1-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726036AbfKHQJY (ORCPT ); Fri, 8 Nov 2019 11:09:24 -0500 Received: by mail-vs1-f47.google.com with SMTP id l5so4111021vsh.12 for ; Fri, 08 Nov 2019 08:09:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GgR8SbJM/LwWNsFT9KWb1wzEtiup6uUwZwyMnR0ES20=; b=A6HKo7SEd/6iRY8fMOWCgHk2G+aH0sCZWuEDpPBzIdu9IY1MzhDq/9LMPpmAMFbFUq 0xVr/8aZo3f4e5NuhVpyE1Ohoq5WVYXReeE7gR4n1T28cZdEhOgSu/+uniaGRXkeIrK5 k7Q+Pbb+/f9EApA2uIbxIYrgXA/sHsZbyObJ/EL0avAtU2DsHimvBRSc3ZEWwk7AnCWg zKiRp8mfD9PdZuj7gkrM8XV4yyA0Z97jE1RqOk7xWxu152sgdiMixyJvyGt4vfPa0Vqb 7a6Is/7ZG7ducw6qIbzpCAgFdIY+Un4f88A6ll3qsadjI9qAx5/Z4rbpIlxeH1dWg9PM 4wNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GgR8SbJM/LwWNsFT9KWb1wzEtiup6uUwZwyMnR0ES20=; b=Gd9KSHpo5zTR8WVvC/QCwb1ygxpXVwq8MBkAbVnMLDMkO8q+IuN0/zMsNyE21WAbch QI/OU2TAO9X1KOTN86HRcd9W63Zemfrir0ZmRj5OINNF6BRNrQ5vyOFu3swMksyYU2lu J6ZIswLzU0qXQbqThZpkR2daEzQEG1GUvNHvHW50so+sJ6tGU4hxtVkfub9pFwdbwAdm RCigVnlB5M1V/QAJQevxdYi7pL2YFy7Hzd2sc9uVBNLpe5Fe1nYFJmPtFd4Q3Akp5nAZ RdFZ1wT68sDwkY7ygAvwpktcIjpDTHLG48rck7QMnl3Tdso2u354fD4bLNwggSUsLLJi 0pXQ== X-Gm-Message-State: APjAAAUvUECSdZRmuRcl4hluJ2yMYrg3lzpLmtzyDFOrx5mE2C97s2fo 7HObzWJ16q9r9hlnguPrwiBePrVgF618lvSc6B5kxA== X-Received: by 2002:a05:6102:21b4:: with SMTP id i20mr8731659vsb.164.1573229361668; Fri, 08 Nov 2019 08:09:21 -0800 (PST) MIME-Version: 1.0 References: <5DBD272A-0D55-4D74-B201-431D04878B43@ascha.org> In-Reply-To: <5DBD272A-0D55-4D74-B201-431D04878B43@ascha.org> From: Olga Kornievskaia Date: Fri, 8 Nov 2019 11:09:10 -0500 Message-ID: Subject: Re: Specific IP per mounted share from same server To: Samy Ascha Cc: linux-nfs Content-Type: text/plain; charset="UTF-8" Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Hi Samy, Are you going against a linux server? I don't think linux server has the functionality you are looking for. What you are really looking for I believe is session trunking and neither the linux client nor server fully support that (though we plan to add that functionality in the near future). Bruce, correct me if I'm wrong but linux server doesn't support multi-home (multi-node?) therefore, it has no ability to distinguish requests coming from different network interfaces and then present different server major/minor/scope values and also return different clientids in that case as well. So what happens now even though the client is establishing a new TCP connection via the 2nd network, the server returns back to the client same clientid and server identity as the 1st mount thus client will use an existing connection it already has. On Fri, Nov 8, 2019 at 3:48 AM Samy Ascha wrote: > > Hi! > > I have an NFS server with 2 NICs, configured on different subnets. These subnets are on different network segments (2 dedicated switches). > > I have clients that mount 2 distinct shares from this server. Expecting to spread the network load, I specified the mounts like so, in fstab: > > 10.110.1.235:/srv/nfs/www /var/www nfs defaults,rw,intr,nosuid,noatime,vers=4.1 0 0 > 10.110.0.235:/srv/nfs/backup /backup nfs defaults,rw,intr,nosuid,noatime,vers=4.1 0 0 > > However, as you may find totally expected, I see both mounts connected to the same IP on the server. Specificly, the one specified for the first mount: > > 10.110.1.235:/srv/nfs/www on /var/www type nfs4 (rw,...) > 10.110.1.235:/srv/nfs/backup on /backup type nfs4 (rw,...) > > Is this expected? Am I wrong to assume that this is a possible setup? If possible/forcible, what am I missing / doing wrong? :) > > Thanks much, > Samy