From owner-freebsd-bugs Wed Jun 20 7:37:27 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 30AC237B401; Wed, 20 Jun 2001 07:37:22 -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 15:37:14 +0100 (BST) To: Peter Pentchev Cc: Jeroen Ruigrok/Asmodai , freebsd-bugs@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 17:02:51 +0300." <20010620170251.B794@ringworld.oblivion.bg> Date: Wed, 20 Jun 2001 15:37:10 +0100 From: Ian Dowse Message-ID: <200106201537.aa99536@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 <20010620170251.B794@ringworld.oblivion.bg>, Peter Pentchev writes: > >I'd love to have umount -f functionality. I'd absolutely LOVE to. >(think NFS server on a laptop, and hung NFS mounts after the laptop > is physically removed..) So would I, but unfortunately that is a different issue :-(. This PR relates to the problem where umount -f fails when the server is alive and responding, but something is holding an extra reference on the filesystem root vnode. This problem also exists in a number of other filesystems in the tree, all of which were fixed in -current by the vflush() changes. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message