On Sat, 18 Apr 2020, Jim Klimov wrote:
Many links I found stress the use of lockd to have the locking at
all. So the rewrite might play a role too. And a mix of NFS v2/3/4
supports might vary a lot - see if downgrading to v3 (forcing vers
in automounter settings) helps for example.
I tried downgrading to v3 and it made no difference at all.
This is an OmniOS to OmniOS NFS mount from a zone on the same system
so the software is assured to be as "compatible" as possible.
I edited the autom4te script and changed:
my $flock_implemented = 'yes';
to
my $flock_implemented = 'no';
and then there were no more complaints about the locking.
Unfortunately, it appears that parallel builds then result in other
errors so this is not a solution. It appears that setting this
parameter to 'no' simply uses no locking at all.
The interesting thing is that testing from an Ubuntu 18.04 Linux
client works "fine" with no obvious concurrency issues or error
messages.
In the Linux mount to the home directory, I see this option mentioned:
'local_lock=none'.
Complete mount options mentioned by Linux are like
(rw,nosuid,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,noacl,
proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=65.66.246.70,mountvers=3,
mountport=59848,mountproto=udp,local_lock=none,addr=63.67.246.72)
Bob
--
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/T62b11c36b038c208-Ma5e0a82b8c4a3900dd0483fb
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
