From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 12 12:00:31 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E48F10656A4 for ; Wed, 12 Oct 2011 12:00:31 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5D2A78FC1E for ; Wed, 12 Oct 2011 12:00:31 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9CC0Ue7021469 for ; Wed, 12 Oct 2011 12:00:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9CC0UrK021466; Wed, 12 Oct 2011 12:00:30 GMT (envelope-from gnats) Date: Wed, 12 Oct 2011 12:00:30 GMT Message-Id: <201110121200.p9CC0UrK021466@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Andrey Simonenko Cc: Subject: Re: kern/85464: Cannot unmount file-backed disk imported from NFS or SMBFS X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrey Simonenko List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2011 12:00:31 -0000 The following reply was made to PR kern/85464; it has been noted by GNATS. From: Andrey Simonenko To: Garrett Cooper Cc: bug-followup@FreeBSD.org Subject: Re: kern/85464: Cannot unmount file-backed disk imported from NFS or SMBFS Date: Wed, 12 Oct 2011 14:06:57 +0300 On Tue, Oct 11, 2011 at 06:35:28PM -0700, Garrett Cooper wrote: > This is to be expected with any version of Unix when not mounting > with -o soft if the underlying filesystem goes away. This isn't a bug but > instead a well known caveat with network-based filesystems. > I suggest closing this bug with that in mind. I described absolutely another bug on 5.4-STABLE. It was impossible to unmount file-backed disk (attached by 'mdconfig -a -t vnode -f ...') from mounted NFS file system on a client system. Since I could not reproduce this bug on 8.2-STABLE with new NFS client and server, this PR can be closed.