Linux NFS development
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: nfs@lists.sourceforge.net
Subject: Help needed with NFS locking
Date: Sat, 19 Jul 2003 12:59:03 -0700	[thread overview]
Message-ID: <3F19A307.3090102@tupshin.com> (raw)

I'm absolutely stuck on this one. I'm running linux-2.4.21-ac4 on both 
client and server (problem is not unique to this version of the kernel), 
with debian-sid distribution on both systems. I'm trying to run /home as 
an NFS-mounted volume on the client, but no matter what I try, I can't 
get nfs-locking to work.

rpcinfo -p on the server looks like this:
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp    665  status
    100024    1   tcp    668  status
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100021    1   udp  41255  nlockmgr
    100021    3   udp  41255  nlockmgr
    100021    4   udp  41255  nlockmgr
    100021    1   tcp  49464  nlockmgr
    100021    3   tcp  49464  nlockmgr
    100021    4   tcp  49464  nlockmgr
    100005    1   udp    728  mountd
    100005    1   tcp    731  mountd
    100005    2   udp    728  mountd
    100005    2   tcp    731  mountd
    100005    3   udp    728  mountd
    100005    3   tcp    731  mountd

and on the client:
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100021    1   udp  32768  nlockmgr
    100021    3   udp  32768  nlockmgr
    100021    4   udp  32768  nlockmgr
    100021    1   tcp  32768  nlockmgr
    100021    3   tcp  32768  nlockmgr
    100021    4   tcp  32768  nlockmgr
    391002    1   tcp    772  sgi_fam
    391002    2   tcp    772  sgi_fam
    100024    1   udp    652  status
    100024    1   tcp    655  status

And doing a remote rpcinfo between the two machines shows the same 
information.

The symptom exihibits itself mainly as an inability to use gnome due to 
file-locking errors, but other applications provide locking warnings as 
well. BTW, is there a canonical way to test for nfs-locking?


Any suggestions???

-Tupshin



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2003-07-19 19:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F19A307.3090102@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox