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
