From owner-freebsd-current Tue Apr 9 16:42:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA29958 for current-outgoing; Tue, 9 Apr 1996 16:42:56 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA29952 for ; Tue, 9 Apr 1996 16:42:53 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.4/8.7.4) with SMTP id TAA00279 for ; Tue, 9 Apr 1996 19:42:46 -0400 (EDT) Date: Tue, 9 Apr 1996 19:42:46 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: Can't nfs mount from stable -> current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... After about 2+days uptime on both my -stable machine and my -current machine, the -current machine once more panic'd with the rlist bug I reported last week. Fine, break out of DDB, reboot the machine, let the fsck's do their thing and... ...no NFS mounts. If I do a 'mount nfs:/home /home' to mount the home directories, I get: NFS Portmap: RPC: Success And then it just hangs. I'm sending this one out as a rushed panic hoping that someone may be able to give me a clue as to what to look, while continuing to look for the bug myself (guess I'm missing DS9 tonight *sigh*) Anyone have any ideas? Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org