Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CACt_J9PHSjkz_-x0K=7+AYjiX1Ur5cV+brC9Tv4i7dkG=NSBuQ@mail.gmail.com>
 <3D87B9ED-3A00-478B-AC17-435B71D0A349@redhat.com>
In-Reply-To: <3D87B9ED-3A00-478B-AC17-435B71D0A349@redhat.com>
From:   jie wang <yjxxtd12@gmail.com>
Date:   Thu, 7 Jul 2022 07:56:44 +0800
Message-ID: <CACt_J9NXmz4WCBT8iAT1MRNnhE1k5DpQct+00t-hTsbZrru06g@mail.gmail.com>
Subject: Re: Question abount sm-notify when use NFSv3 lock
To:     Benjamin Coddington <bcodding@redhat.com>
Cc:     linux-nfs@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Thanks the reply, I have tried it, but it doesn't work, '-v' can only
use the local address


On Wed, Jul 6, 2022 at 10:39 PM Benjamin Coddington <bcodding@redhat.com> wrote:
>
> On 6 Jul 2022, at 8:28, jie wang wrote:
>
> > Hi, all
> >   When we use NFSv3, we have a LoadBalance in front of NFS server. For
> > example, LoadBalance's ip is ip2 and NFS server's ip is ip1, and
> > client use ip2 to mount.
> >
> >   Now client use flock to lock file, then I restart NFS server and
> > execute sm-notify -f. Then the problem occurs, the sm-notify request's
> > src ip is ip1, not ip2, so rpc.statd will ignore this notify, because
> > it does not match ip2 when mount, so client will not reclaim lock, and
> > lock lost when restart NFS server.
> >
> >   Do you know how to address this ? Thanks a lot.
>
> The sm-notify(8) man page shows you can use '-v' to specify an ipaddr or
> hostname.
>
> Ben
>