From owner-freebsd-current  Mon Jun  1 12:47:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA14944
          for freebsd-current-outgoing; Mon, 1 Jun 1998 12:47:38 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14928
          for <current@FreeBSD.ORG>; Mon, 1 Jun 1998 12:47:32 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id OAA21359;
	Mon, 1 Jun 1998 14:47:01 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199806011947.OAA21359@home.dragondata.com>
Subject: Re: NFS discovery
In-Reply-To: <199806011908.DAA10546@spinner.netplex.com.au> from Peter Wemm at "Jun 2, 98 03:08:23 am"
To: peter@netplex.com.au (Peter Wemm)
Date: Mon, 1 Jun 1998 14:47:00 -0500 (CDT)
Cc: mi@video-collage.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 
> > That's my thought too, but:
> > 
> > umount /home
> > 
> > will freeze, so it's not exactly unmounting things. :)
> 
> That's because umount (in it's infinite wisdom) tries to stat() the
> argument to see what file type (/dev node) or directory it is (and resolve
> symlinks and other wierd things).  This causes the NFS hang.
> 
> I was debating whether to remove it so that it worked solely from the vfs 
> mount list.

How about an option to control it? :)

> 
> Incidently,
> 	umount -f -t nfs server:/home
> usually works, as long as the VFS layer isn't deadlocked on the mountlist 
> or a busy filesystem.  This is because stat("server:/home") fails with an 
> ENOENT rather than doing a nfs operation.  Definately a ``feature'' if I 
> ever saw one.

I tried that too, and umount would freeze. (I could at least ^C out of it
though)

> > 
> > Don't read my post as a complaint, rather as a 'hey, why does it do this?"
> > :)
> 
> Is it consistant BTW?  Or are you not willing to do blow away your server 
> again? :-)

I discovered it a few days ago, during massive power problems. (the servre
kept rebooting randomly) and it worked every time. I'm about to reboot the
server again, and can test whatever is needed. 

Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message