Hi.

autom4te tries to use flock() over NFS but NFS doesn't supports that.

Gergő

Bob Friesenhahn <[email protected]> ezt írta (időpont: 2020.
ápr. 17., P, 22:05):

> I have an OmniOS system (omnios-r151030-521a1fc4d1) which exports home
> directories via NFS.  From a Zone on the same system, I use a per-user
> home directory NFS automount to access the home directories.
>
> While attempting to use GNU Autotools (with source files accessed via
> the NFS mount), I encounter this problem:
>
> autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
>
> From what I have read this indicates either that the NFS locking is
> not working properly or that a necessary Perl interface to do the
> locking is not working.
>
> The Perl being used comes from 'pkgsrc' installation.
>
> A week ago, this Zone was accessing home directories on a Solaris 10
> server and it had the exact same issues so it seems most likely that
> the issue is with Perl or the Zone itself.  It seems to me that this
> issue may have been added by an OmniOS update since at one time it did
> not occur.
>
> I tried replacing the perl executable used with OmniOS's /usr/bin/perl
> but the same problem occurs, so the problem must not be specific to
> pkgsrc's Perl.
>
> If I execute the Autotools commands on a Linux system which has NFS
> mounts to the same server, there is no problem.
>
> If I execute the Autotools commands from an old OpenIndiana system
> (5.11 oi_151a9), there is no problem.
>
> Everything is pointing to some issue with the Zone.
>
> These is the status of NFS related services on the Zone:
>
> % svcs -a |grep nfs
> disabled       Apr_11   svc:/network/nfs/client:default
> disabled       Apr_11   svc:/network/nfs/server:default
> disabled       Apr_11   svc:/network/nfs/log:default
> disabled       Apr_11   svc:/network/nfs/rquota:default
> online         Apr_11   svc:/network/nfs/cbd:default
> online         Apr_11   svc:/network/nfs/mapid:default
> online         Apr_11   svc:/network/nfs/status:default
> online         Apr_11   svc:/network/nfs/nlockmgr:default
> 
> and these appear to be similar to the oi_151a9 system which is
> working.
> 
> I tried enabling svc:/network/nfs/client:default in the Zone, but it
> made no difference.
> 
> These are the services enabled on the server side:
> 
> disabled       Apr_11   svc:/network/nfs/log:default
> online         Apr_11   svc:/network/nfs/cbd:default
> online         Apr_11   svc:/network/nfs/mapid:default
> online         Apr_11   svc:/network/nfs/status:default
> online         Apr_11   svc:/network/nfs/nlockmgr:default
> online         Apr_11   svc:/network/nfs/rquota:default
> online         Apr_11   svc:/network/nfs/client:default
> online         Apr_11   svc:/network/nfs/server:default
> 
> The mount options used by the Zone (and OpenIndiana) are listed as:
> 
> remote/read/write/setuid/nodevices/xattr/zone=swdev/dev=8780007
> 
> Does anyone have any ideas regarding how to solve this problem?
> 
> Is there a Zone option which needs to be enabled in order to use NFS
> locking?
> 
> 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-M15f6989218b49429fa601444
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

Reply via email to