Re: Question abount sm-notify when use NFSv3 lock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx> 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
>



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux