Linux-NFS Archive on
 help / color / Atom feed
From: Olga Kornievskaia <>
To: Samy Ascha <>
Cc: linux-nfs <>
Subject: Re: Specific IP per mounted share from same server
Date: Fri, 8 Nov 2019 11:09:10 -0500
Message-ID: <> (raw)
In-Reply-To: <>

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

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:
>    /var/www    nfs defaults,rw,intr,nosuid,noatime,vers=4.1 0 0
>    /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:
> on /var/www type nfs4 (rw,...)
> 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

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  8:41 Samy Ascha
2019-11-08 16:09 ` Olga Kornievskaia [this message]
2019-11-08 16:29   ` bfields
2019-11-08 17:06     ` Olga Kornievskaia
2019-11-08 17:15       ` J. Bruce Fields

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-NFS Archive on

Archives are clonable:
	git clone --mirror linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ \
	public-inbox-index linux-nfs

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone