From owner-freebsd-bugs@FreeBSD.ORG Mon Mar 12 10:30:11 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E72716A403 for ; Mon, 12 Mar 2007 10:30:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 393BF13C487 for ; Mon, 12 Mar 2007 10:30:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2CAUA9C061553 for ; Mon, 12 Mar 2007 10:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2CAU9l0061552; Mon, 12 Mar 2007 10:30:09 GMT (envelope-from gnats) Date: Mon, 12 Mar 2007 10:30:09 GMT Message-Id: <200703121030.l2CAU9l0061552@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Remko Lodder Cc: Subject: Re: misc/110213: umount doesn't deallocate the md device after an mfs filesystem X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Remko Lodder List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2007 10:30:11 -0000 The following reply was made to PR misc/110213; it has been noted by GNATS. From: Remko Lodder To: Gergely Czuczy Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/110213: umount doesn't deallocate the md device after an mfs filesystem Date: Mon, 12 Mar 2007 11:27:53 +0100 On Mon, Mar 12, 2007 at 10:08:10AM +0000, Gergely Czuczy wrote: > > FreeBSD luggage.in.publishing.hu 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #0: Fri Mar 9 17:22:07 UTC 2007 toor@blinky:/usr/obj/usr/src/sys/LUGGAGE i386 > > >Description: > i've played around with mount_mfs to have a pre-prepared mfs filesystem at startup, and i mounted/umounted it several times after modifying my fstab. > at the end, the result was: > # ls -lh /dev/md* > crw-r----- 1 root operator 0, 103 Mar 12 09:55 /dev/md0 > crw-r----- 1 root operator 0, 104 Mar 12 09:55 /dev/md1 > crw-r----- 1 root operator 0, 105 Mar 12 09:55 /dev/md2 > crw-r----- 1 root operator 0, 106 Mar 12 09:55 /dev/md3 > crw-r----- 1 root operator 0, 107 Mar 12 09:58 /dev/md4 > crw------- 1 root wheel 0, 56 Mar 12 09:20 /dev/mdctl > # mount > /dev/md4 on /mnt/keys (ufs, local, soft-updates) > > seems like after umounting an mfs filesystem the system leaves some dirt behind. > >How-To-Repeat: > 1) make an mfs entry in fstab > 2) mount it and umount it > 3) repeat 2) a few times > 4) check the allocated md devices by ls /dev/md* > > >Fix: > i don't have. > but umount should handle it automaticly :) > >Release-Note: This has nothing to do with mount/umount actually. This only makes the connection between some filesystem and the operating system. The md devices you are seeing are symbolic references to either a file (in your case) or real disks. if you want to get rid of them you should use mdconfig(8) (mdconfig -d -u md1 (substitute this with the number the device you are currently using)). Regards, Remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */