From owner-freebsd-current@FreeBSD.ORG Wed Feb 2 10:13:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B607516A4CE for ; Wed, 2 Feb 2005 10:13:10 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83F9643D2D for ; Wed, 2 Feb 2005 10:13:10 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id DA4DF46B2D; Wed, 2 Feb 2005 05:13:09 -0500 (EST) Date: Wed, 2 Feb 2005 10:12:25 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Niclas Zeising In-Reply-To: <42008FDC.6050400@n00b.apagnu.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: unmount of /dev failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 02 Feb 2005 10:13:10 -0000 On Wed, 2 Feb 2005, Niclas Zeising wrote: > I am using current as of yesterday (20050201) morning CET (around 0800 i > think). When I shutdown or reboot my system (shutdown -[h,r] now) it > runs through the shut down sequence as usual, but right before it is > rebooting or the message about the shutdown complete comes up, when > unmouning dev, it complains about "unmount of /dev failed (BUSY)" before > shutting down as usual. Is this a bug, and if so, common or known? Or > am I just being stupid somewhere and all is my fault? Just let me know > if I need to provide more information. I'm guessing this started occuring because phk changed devfs not to permit forceable unmount due to some nasty issues involved (devfs_vfsops.c:1.41). And, for some reason, we presumably have a lingering reference to devfs -- perhaps the root file system mounted from a devfs vnode, another feature introduced recently? It's probably non-harmful, but probably also should be fixed by properly unwinding and unmounting devfs at the right moment in the shutdown to reflect changes in the boot order. Robert N M Watson