From hsu@clinet.fi  Mon Jan  1 16:06:08 1996
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA17201
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 1 Jan 1996 16:06:04 -0800 (PST)
Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id CAA01057 for <FreeBSD-gnats-submit@freebsd.org>; Tue, 2 Jan 1996 02:06:00 +0200
Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id CAA12099; Tue, 2 Jan 1996 02:06:05 +0200
Message-Id: <199601020006.CAA12099@katiska.clinet.fi>
Date: Tue, 2 Jan 1996 02:06:05 +0200
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: Mounting nfs disks before starting mountd: Chicken or Egg problem
X-Send-Pr-Version: 3.2

>Number:         926
>Category:       bin
>Synopsis:       Mounting nfs disks before starting mountd: Chicken or Egg problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jan  1 16:10:01 PST 1996
>Closed-Date:    Mon Apr 13 01:37:24 PDT 1998
>Last-Modified:  Mon Apr 13 01:37:39 PDT 1998
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2-CURRENT i386
>Organization:
Clinet, Espoo, Finland
>Environment:

	Machine A:  nfs server, but also mounts disks from B.  Primary name
	server.

	Machine B:  nfs server, but also mounts disks from A. 

>Description:

	Two problems:

	A only crashes:  locks up in mount -a -t nfs, as B does not get
	name server replies.  This probably is a problem in mount, as it
	should try secondary name servers, but apparently it does not.

	A and B both crash (this happens often, as after A crashes B goes
	into a deadlock in the nfs code).  Both get stuck in
	mount -a -t nfs, as neither system has mountd running yet.
	Breaking mount from either machine gets them up, one without nfs
	disks.

>How-To-Repeat:

	Set up two FreeBSD machines to mount each others disks and reboot
	both of the simultaneously. 

>Fix:
	
	I am trying moving mount -a -t nfs after starting mountd and nfsiod in
	/etc/rc.  We will see what happens with the next crash.
	
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:16:03 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->open 
State-Changed-By: scrappy 
State-Changed-When: Tue Oct 22 01:42:07 PDT 1996 
State-Changed-Why:  

Problem Still Exists 

-- 

From: Heikki Suonsivu <hsu@clinet.fi> 

This is still valid problem; mountd is started in /etc/rc later than mount 
-a -t nfs is run (checked current from two days ago). 


From: Peter Wemm <peter@spinner.DIALix.COM>
To: Robert Eckardt <roberte@mep.ruhr-uni-bochum.de>
Cc: scrappy@freefall.freebsd.org (Marc G. Fournier), hsu@clinet.fi,
        freebsd-gnats-submit@freefall.freebsd.org
Subject: Re: bin/926 
Date: Tue, 22 Oct 1996 20:37:47 +0800

 Robert Eckardt wrote:
 > > Synopsis: Mounting nfs disks before starting mountd: Chicken or Egg problem
 > > Problem Still Exists
 
 > > From: Heikki Suonsivu <hsu@clinet.fi>
 > > 
 > > This is still valid problem; mountd is started in /etc/rc later than mount
 > > -a -t nfs is run (checked current from two days ago).
 > 
 > This is no conflict. mountd is needed for the NFS-Server.
 > Mounting NFS-FSs is done by the NFS-Client, which needs only nfsiod.
 > 
 > Robert
 
 And not even that.. You can mount nfs partitions as a client even without 
 the nfsiod's running, you just get slower transfers until they are going.
 
 Although I could see there would be a problem if the machine was mounting 
 some of it's own disks, but I suspect that might be tempting fate with 
 ``interesting'' coherency problems..
 
 Cheers,
 -Peter
 
 

From: Heikki Suonsivu <hsu@clinet.fi>
To: freebsd-gnats-submit@freebsd.org
Cc: hsu@clinet.fi
Subject: bin/926 Mounting nfs disks before starting mountd: Chicken or Egg problem
Date: Sat, 28 Mar 1998 04:30:02 +0200 (EET)

 I think this has been fixed, now mountd is started in rc.network, which is
 run before mount -a -t nfs.  I haven't verified this, as our NFS servers
 have older /etc, but it now looks right.
 
 Studded@dal.net writes:
  > Greetings, :)
  > 
  > 	I am writing to you in regards to your FreeBSD Problem
  > Report. The FreeBSD project is currently conducting a beta test on
  > version 2.2.6 and feedback as to whether you are still experiencing
  > your problem would be very valuable. 
  > 
  > 	If you are still experiencing the problem you reported, it
  > would help the project track the problem if you could upgrade to the
  > latest snapshot of 2.2.6-Beta (located at releng22.freebsd.org) and
  > test your problem again. 
  > 
  > 	If you have any feedback regarding this Problem Report,
  > whether you are still experiencing the problem or whether the PR can
  > be closed, please mail your response to
  > freebsd-gnats-submit@freebsd.org. Please do not respond directly to
  > me. I am merely a humble volunteer and have no official connection to
  > the FreeBSD project. Therefore I cannot make any changes to the status
  > of your Problem Report. It is also very important that you include 
  > the category and number of your Problem Report (bin/926)
  > in the subject line of your response.
  > 
  > 	Another option if you need a refresher on the details of your
  > problem or would like to submit a followup is to use the web page
  > interface and look up your PR by number.
  > http://www.freebsd.org/cgi/query-pr-summary.cgi
  > 
  > 	Thank you for helping to make this the greatest release of
  > FreeBSD ever.
  > 
  > Doug
  > 
  > 
  > -- 
  > ***         Chief Operations Officer, DALnet IRC network       ***
  > *** Proud operator, designer and maintainer of the world's largest
  > *** Internet Relay Chat server.  5,328 clients and still growing.
  > *** Try spider.dal.net on ports 6662-4    (Powered by FreeBSD)
  > 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Mon Apr 13 01:37:24 PDT 1998 
State-Changed-Why:  
looks like we fixed it. 
>Unformatted:
