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;
From:   "Benjamin Coddington" <bcodding@redhat.com>
To:     "jie wang" <yjxxtd12@gmail.com>
Cc:     linux-nfs@vger.kernel.org
Subject: Re: Question abount sm-notify when use NFSv3 lock
Date:   Thu, 07 Jul 2022 07:51:53 -0400
Message-ID: <68BD4FDC-A409-422A-BE3F-318AEC8F3134@redhat.com>
In-Reply-To: <CACt_J9NtB5+1MiL8JrNbyLf6uhgHWDYmyAtKgmKdhzMkgL9E5g@mail.gmail.com>
References: <CACt_J9PHSjkz_-x0K=7+AYjiX1Ur5cV+brC9Tv4i7dkG=NSBuQ@mail.gmail.com>
 <3D87B9ED-3A00-478B-AC17-435B71D0A349@redhat.com>
 <CACt_J9NXmz4WCBT8iAT1MRNnhE1k5DpQct+00t-hTsbZrru06g@mail.gmail.com>
 <CACt_J9NtB5+1MiL8JrNbyLf6uhgHWDYmyAtKgmKdhzMkgL9E5g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Precedence: bulk

On 6 Jul 2022, at 19:57, jie wang wrote:

> If execute "sm-notify -f -v ip2", sm-notify did not send the notify 
> request.

Hmm, maybe its a bug?  You can turn up debugging with the "-d" opt, 
adding
more increases vebosity.  Try using three of them:

sm-notify -ddd -f -v ip2

Have you tried looking at an strace?  Are there different values set for
sm-notify in your nfs.conf file?

Check out the source, perhaps sm-notify isn't going to be able to send a
notification for an address that doesn't exist on a local network 
adapter
(this is a common pattern), and you need to configure that ip address as 
an
additional address on your system?

These are guesses.

Ben