All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chip Salzenberg <chip@pobox.com>
To: Christoph Simon <ciccio@kiosknet.com.br>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS lock and timeout problems
Date: Sat, 21 Sep 2002 22:05:25 -0400	[thread overview]
Message-ID: <20020922020525.GC30397@perlsupport.com> (raw)
In-Reply-To: <20020913144548.455bc477.ciccio@kiosknet.com.br>

According to Christoph Simon:
> The server is a debian sid machine with an unpatched 2.4.19 kernel und
> the official debian packages for the kernel server. The client is a
> debian 3.0 (stable) machine with the same kernel, but having only NFS
> client compiled into it, not the kernel nfs server.

Caveat: I don't really know what's going wrong.

However, I think this may be part of the problem:

> /etc/hosts.allow on the client has:
> 	portmap: 192.168.254.15
> 	lockd:   192.168.254.15
> 	rquotad: 192.168.254.15
> 	mountd:  192.168.254.15
> 	statd:   192.168.254.15

The client needs to be able to communicate with itself.  You should
probably have "ALL: 127.0.0.1" in there as well.

Also, in a possibly unrelated matter, I suggest that the client mount
a ramdisk on /var before statd runs from /etc/init.d/nfs-common starts
statd.  Make sure that /var/lib/nfs exists before you start.  This is
probably a good idea anyway given that you surely don't want lots of
clients sharing /var.

> 	nsm_mon_unmon: rpc failed, status=-13
> 	lockd: cannot monitor 192.168.254.15
> 	lockd: failed to monitor 192.168.254.15
> 
> I tried to trace the command from the rcS.d scripts which would cause
> them, and, if there is no delay, the first comes in checkroot.sh, when
> "mount -f -o remount /" is given. I've read that status=-13 tells that
> statd is missing, but at this time it's running on the server and on
> the client [...]

How is it running on the client?  IIRC, checkroot.sh runs long before
'/etc/init.d/nfs-common start'.

> I also found it strange, that "cat /proc/mount" on the client will
> always give:
> 
> 	192.168.254.15:/nfsvol / \
> 	  nfs rw,v3,rsize=8192,wsize=8192,hard,udp,lock,addr=192.168.254.15
> 
> where v3, rsize, wsize, udp and lock are options I never gave.

Those are the defaults for the given options.

> read that the defaults for rsize,wsize is 1024,

That was long ago.  Nowadays, 8K is the default.
-- 
Chip Salzenberg         - a.k.a.  -        <chip@pobox.com>
         "It furthers one to have somewhere to go."


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2002-09-22 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 17:45 NFS lock and timeout problems Christoph Simon
2002-09-22  2:05 ` Chip Salzenberg [this message]

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=20020922020525.GC30397@perlsupport.com \
    --to=chip@pobox.com \
    --cc=ciccio@kiosknet.com.br \
    --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.