All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Sedlacek <jan.sedlacek@asicentrum.cz>
To: nfs@lists.sourceforge.net
Subject: NFS server RH7.1, kernel 2.4.18, client Solaris 7
Date: Mon, 25 Mar 2002 14:28:31 +0100	[thread overview]
Message-ID: <3C9F25FF.1000203@asicentrum.cz> (raw)

Hi all,

    I have the following problem,

I've upgraded to RedHat Linux 7.1 with kernel 2.4.18 (compiled with 
options NFSv3 server and client support checked). Clients are RH Linux 
6.1, 6.2, 7.0, 7.1 and Solaris 7.
Linux clients work fine without any problem. Solaris 7 clients work fine 
only without locking files. If I try on Solaris to start old openwindows 
file manager (filemgr) it hangs for five minutes and reports just 
"nfs-server: RPC timed out". I think the problem is locking files. I 
tried on NFS server to set "insecure_locks" and "no_auth_nlm" options in 
/etc/exports file, but it didn`t help.

NFS server rpcinfo shows:

   program verz proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32768  status
    100007    2   udp    781  ypbind
    100007    1   udp    781  ypbind
    100007    2   tcp    784  ypbind
    100007    1   tcp    784  ypbind
    100011    1   udp    735  rquotad
    100011    2   udp    735  rquotad
    100005    1   udp  32889  mountd
    100005    1   tcp  32845  mountd
    100005    2   udp  32889  mountd
    100005    2   tcp  32845  mountd
    100005    3   udp  32889  mountd
    100005    3   tcp  32845  mountd
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp  32890  nlockmgr
    100021    3   udp  32890  nlockmgr
    100021    4   udp  32890  nlockmgr                  

,so lock manager is running (as rpc.statd is running).

Any idea is very appreciated.

Regards,

Sedlon




_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2002-03-25 13:28 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=3C9F25FF.1000203@asicentrum.cz \
    --to=jan.sedlacek@asicentrum.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.