From owner-freebsd-bugs Wed Jun 20 6:27:37 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 6B52337B406; Wed, 20 Jun 2001 06:27:35 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Jun 2001 14:27:33 +0100 (BST) To: freebsd-bugs@FreeBSD.org Cc: asmodai@FreeBSD.org Subject: Re: kern/765: umount -f can`t umount a NFS filesystem in use In-Reply-To: Your message of "Wed, 20 Jun 2001 06:15:35 PDT." <200106201315.f5KDFZB73481@freefall.freebsd.org> Date: Wed, 20 Jun 2001 14:27:33 +0100 From: Ian Dowse Message-ID: <200106201427.aa85395@salmon.maths.tcd.ie> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <200106201315.f5KDFZB73481@freefall.freebsd.org>, asmodai@FreeBSD.or g writes: >Synopsis: umount -f can`t umount a NFS filesystem in use > >Responsible-Changed-From-To: asmodai->freebsd-bugs This has been fixed in -current (revision 1.312 of vfs_subr.c and associated changes), but is still a problem in -stable. A direct MFC would require the recompilation of all filesystem modules, and minor source changes to any filesystems maintained outside the tree. Is this likely to cause problems? If so, an alternative would be a workaround that would just fix the NFS case. I'd prefer to reduce rather than increase the differences between the branches if possible though. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message