search for: nlockmgr

...rts on NFS server ************************* /nfsroot *(rw,sync,no_root_squash) rpcinfo -p output on NFS server program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100021 1 udp 1090 nlockmgr 100021 3 udp 1090 nlockmgr 100021 4 udp 1090 nlockmgr 100021 1 tcp 1036 nlockmgr 100021 3 tcp 1036 nlockmgr 100021 4 tcp 1036 nlockmgr 100005 1 udp 738 mountd 100005 1 tcp 741 mountd 100005 2 udp 738 mountd 100005 2 tcp 741 mountd 100005 3 udp 738 mountd 100005 3 tcp 741 mountd NFS server is Ubunt...

...e search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help. root at saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp 4004 rquotad 100011 2 udp 4004 rquotad 100011 1 tcp 4004...

...e pormap service. I've even tried restarting the network service, but unfortunately nothing seems affected: [root at stallion:/etc/init.d] $ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 55394 nlockmgr 100021 3 udp 55394 nlockmgr 100021 4 udp 55394 nlockmgr 100021 1 tcp 33704 nlockmgr 100021 3 tcp 33704 nlockmgr 100021 4 tcp 33704 nlockmgr 100024 1 udp 786 status 100024 1 tcp 789 status Does anyone have any tips on...

...100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100003 4 tcp 2049 nfs 100003 4 udp 2049 nfs 100021 1 udp 55700 nlockmgr 100021 3 udp 55700 nlockmgr 100021 4 udp 55700 nlockmgr 100021 1 tcp 52795 nlockmgr 100021 3 tcp 52795 nlockmgr 100021 4 tcp 52795 nlockmgr

...662 status 100011 1 udp 875 rquotad 100011 2 udp 875 rquotad 100011 1 tcp 875 rquotad 100011 2 tcp 875 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100021 1 udp 32769 nlockmgr 100021 3 udp 32769 nlockmgr 100021 4 udp 32769 nlockmgr 100021 1 tcp 32803 nlockmgr 100021 3 tcp 32803 nlockmgr 100021 4 tcp 32803 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs...

...768 status 391002 2 tcp 32769 sgi_fam 100011 1 udp 639 rquotad 100011 2 udp 639 rquotad 100011 1 tcp 642 rquotad 100011 2 tcp 642 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 32787 nlockmgr 100021 3 udp 32787 nlockmgr 100021 4 udp 32787 nlockmgr 100005 1 udp 32788 mountd 100005 1 tcp 32815 mountd 100005 2 udp 32788 mountd 100005 2 tcp 32815 mountd 100005 3 udp 32788 mountd 100005 3 tcp 32815 mountd...

...597 mountd 100005 1 tcp 597 mountd 100005 2 udp 597 mountd 100005 2 tcp 597 mountd 100005 3 udp 597 mountd 100005 3 tcp 597 mountd 100003 3 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100021 1 udp 599 nlockmgr 100021 3 udp 599 nlockmgr 100021 4 udp 599 nlockmgr 100021 1 tcp 599 nlockmgr 100021 3 tcp 599 nlockmgr 100021 4 tcp 599 nlockmgr 100011 1 udp 598 rquotad 100011 2 udp 598 rquotad 100011 1 tcp 598...

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > we are using ctdb 4.15.5 on RHEL8 (Kernel > 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 > clients. Whenever an ip takeover happens most clients report > something like this: > [Mon Feb 13 12:21:22

...portmapper 100000 2 udp 111 portmapper 100024 1 udp 54233 status 100024 1 tcp 32813 status 100005 2 udp 20048 mountd 100005 2 tcp 20048 mountd 100003 4 tcp 2049 nfs 100003 4 udp 2049 nfs 100021 3 udp 56990 nlockmgr 100021 3 tcp 40572 nlockmgr # systemctl status nfs ? nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled) Active: active (exited) since Wed 2017-07-05 16:07:06 UTC; 5 days ago Main PID: 130933...

-bash-3.2$ zfs share tank cannot share ''tank'': share(1M) failed -bash-3.2$ how do i figure out what''s wrong? This message posted from opensolaris.org

I started sharing out zfs filesystems via NFS last week using sharenfs=on. That seems to work fine until I reboot. Turned out the NFS server wasn''t enabled - I had to enable nfs/server, nfs/lockmgr and nfs/status manually. This is a stock SXCR b49 (ZFS root) install - don''t think I''d changed anything much. Shouldn''t a ZFS share be permanently enabling NFS?

Hi, we have a new fileserver running on X4275 hardware with Solaris 10U8. On this fileserver we created one test dir with quota and mounted these on another Solaris 10 system. Here the quota command didnot show the used quota. Does this feature only work with OpenSolaris or is it intended to work on Solaris 10? Here what we did on the server: # zfs create -o mountpoint=/export/home2

...ir machine. > > Mike You didn't state what version of NFS you're using.? We're still on nfsv3.? What you're describing looks like an issue with locked. Curious:? Try giving the login ~10 minutes to see if something 'gives up.' On the nfs server:? rpcinfo -p Look at nlockmgr ports & protocols.? My hunch is your dst ports reported are listed. On CentOS 7 & 8, I lock down ports on my clients and server using /etc/nfs.conf (c8) or /etc/sysconfig/nfs (c7).? I used random high numbers, pick your own to taste: $ egrep -v '^($|#)' /etc/nfs.conf [general] [ex...

...th no Samba. Ie: I would like to export NFS shares as CIFS shares using Samba. But: I want file locking. StarOffice 8/OO2.0 support file locking, whereby the first user to open a file will place a lock* on the file, and the other users will get a read-only file. This works fine with NFS & nlockmgr (cross platform, linux/solaris). However, when I add Samba to the mix, it doesn't seem to see the locks. I am under the impression this is because Solaris does not support kernel oplocks. Here is my smb.conf: ---smb.conf--- [global] workgroup = test security = share [shared] path = /ex...

On Fri, Nov 20, 2020 at 12:18 PM Frank Cox <theatre at sasktel.net> wrote: > > On Fri, 20 Nov 2020 12:07:40 -0500 > Michael B Allen wrote: > > > So TCP src 760 to 41285. What's that? > > Apparently "that" is what you need to allow in order for your desktop to work. > > What it is actually doing, I'm not sure. Google tells me that port 760 has

...; : > > > : > On server5, the following services are running; > > : > > > : > root at server5:/var/adm# svcs | grep nfs > > : > online May_25 svc:/network/nfs/status:default > > : > online May_25 svc:/network/nfs/nlockmgr:default > > : > online May_25 svc:/network/nfs/cbd:default > > : > online May_25 svc:/network/nfs/mapid:default > > : > online May_25 svc:/network/nfs/rquota:default > > : > online May_25 svc:/network/nfs/client:default &gt...

...unning 4.0d, I receive the following error: ERROR: No locking available. Running Samba would be unsafe configure: error: summary failure. Aborting config Most directories are mounted using nfs v2 or nfs v3. rpc.lockd and rpc.statd are running on servers and clients. The rpcinfo -p command shows nlockmgr and llockmgr running on both systems. Other than configure's failure to find fcntl or fnctl64 (see below) I can't figure out what might be wrong. Attempting to configure samba 2.0.7 fails with the same error. Anyone have any ideas? TIA. don -------------- Configure results -----------...