From owner-freebsd-current@FreeBSD.ORG Wed Feb 2 11:02:13 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 E51E716A4CE; Wed, 2 Feb 2005 11:02:13 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35C3343D45; Wed, 2 Feb 2005 11:02:13 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j12B2Bp6034030; Wed, 2 Feb 2005 12:02:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 02 Feb 2005 10:12:25 GMT." Date: Wed, 02 Feb 2005 12:02:11 +0100 Message-ID: <34029.1107342131@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org cc: Niclas Zeising 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 11:02:14 -0000 In message , Robert Watson writes: >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. It's on my list, but since it doesn't hurt the on-disk filesystems it is not a high priority. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.