From owner-freebsd-current@FreeBSD.ORG Wed Jun 3 23:52:35 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB41F1065673 for ; Wed, 3 Jun 2009 23:52:35 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 75F348FC16 for ; Wed, 3 Jun 2009 23:52:33 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1MC0G0-0005lg-OS; Thu, 04 Jun 2009 03:52:32 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 5241CB878; Thu, 4 Jun 2009 03:52:27 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 44E54108839; Thu, 4 Jun 2009 03:52:27 +0400 (MSD) Date: Thu, 4 Jun 2009 03:52:27 +0400 From: Dmitry Marakasov To: "O. Hartmann" Message-ID: <20090603235227.GB15659@hades.panopticon> References: <4A2504AA.1020406@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4A2504AA.1020406@zedat.fu-berlin.de> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-current@FreeBSD.org Subject: Re: RPCPROG_MNT: RPC: Timed out / receiving NFS error when trying to mount NFS file system after make world X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 23:52:36 -0000 * O. Hartmann (ohartman@zedat.fu-berlin.de) wrote: Just my 2 cents: the same behaviour, and while mount -o tcp succeeds, umounting behaves strangely: if I umount nfs filesystem, umount process hangs for some time, then exits with `umount: hive: RPCMNT_UMOUNT: RPC: Timed out', while the filesystem is actually umounted immediately after umount is called. This all also breaks amd severely (however it already haven't been working on current for a long time for me). -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru