All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Freedman <freedman@physics.cornell.edu>
To: nfs@lists.sourceforge.net
Subject: Re: NFS problems across reboot
Date: Sun, 7 Apr 2002 01:39:53 -0500	[thread overview]
Message-ID: <20020407063953.GA30304@physics.cornell.edu> (raw)
In-Reply-To: <15535.55222.401084.736426@notabene.cse.unsw.edu.au>

On Sun, Apr 07, 2002, Neil Brown wrote:
> Show us the relevent /etc/init.d file.
> My guess is that "exportfs -a" is being run *After* rpc.nfsd.
> It must must run *before* for correct operation.
> 
> NeilBrown

Hi,

I just checked the default NFS server init script from Debian stable (2.2)
as found in '/etc/init.d/nfs-kernel-server'.  It appears to violate the
above order, by starting exportfs *after* rpc.nfsd.  Am I missing something,
please?

****  Snippet from script listed below:

case "$1" in
  start)
          if grep -q '^/' /etc/exports; then
                   printf "Starting $DESC:"
		   printf " nfsd"
		   start-stop-daemon --start --quiet \
                        --exec $PREFIX/sbin/rpc.nfsd -- $RPCNFSDCOUNT
		   printf " mountd"
		   start-stop-daemon --start --quiet \
                        --exec $PREFIX/sbin/rpc.mountd -- $RPCMOUNTDOPTS
		   echo "."

		   printf "Exporting directories for $DESC..."
                   $PREFIX/sbin/exportfs -r
		   echo "done."
	  else
		   echo "Not starting $DESC: No exports."
          fi
	  ;;
		
		

Upon further inspection, I'm probably not missing something, since when I
checked a Debian woody (3.0) NFS server I'm also maintaining, it has
'exportfs' before the 'rpc.nfsd' call, as you taught me above (I'm grateful
to have learned more on this).  I'm a little surprised this fix wasn't
backported to Debian potato (even though they are understandably cautious to
introduce non-security related changes)...  I guess I'll have to change it
myself in the initscript while still using the potato box.

Could this explain why I've seen the same behaviour as described in an
earlier post in this thread: in other words, when the NFS server cleanly
reboots, all clients with open file handles develop difficulty with NFS
access (sorry I can't remember exact error, it hasn't happened in months);
come to think of it, though, I don't have this problem with my Debian woody
NFS server, which has the correct 'exportfs'/'rpc.nfsd' order in the
init-scripts.

Thanks so much, and take care,
Daniel

-- 
Daniel A. Freedman
Laboratory for Atomic and Solid State Physics
Department of Physics
Cornell University

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

  parent reply	other threads:[~2002-04-07  6:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 19:27 NFS problems across reboot David Ford
2002-04-05  9:12 ` James Pearson
2002-04-07  4:43   ` David Ford
2002-04-07  5:23     ` Neil Brown
2002-04-07  5:44       ` Neil Brown
2002-04-07  6:48         ` David Ford
2002-04-08 13:42         ` James Pearson
2002-04-08 15:23           ` James Pearson
2002-04-08 23:10             ` Neil Brown
2002-04-07  6:39       ` Daniel Freedman [this message]
2002-04-08  2:50         ` Neil Brown
2002-04-07  6:59       ` David Ford
2002-04-08  2:48         ` Neil Brown
2002-04-08 12:15           ` Andreas Unterluggauer
2002-04-08 22:58             ` Neil Brown
     [not found] <E16uI1v-00067H-00@usw-sf-list1.sourceforge.net>
2002-04-08  0:43 ` Al Borchers

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=20020407063953.GA30304@physics.cornell.edu \
    --to=freedman@physics.cornell.edu \
    --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.