From owner-freebsd-current Sun Jun 17 11:10:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id CE0FB37B408 for ; Sun, 17 Jun 2001 11:10:41 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 7153C3E0B; Sun, 17 Jun 2001 11:10:41 -0700 (PDT) To: Jens Schweikhardt Cc: FreeBSD current Subject: Re: mdconfig/umount Fatal trap 12 In-Reply-To: <20010617121217.A2453@schweikhardt.net>; from schweikh@schweikhardt.net on "Sun, 17 Jun 2001 12:12:17 +0200" Date: Sun, 17 Jun 2001 11:10:41 -0700 From: Dima Dorfman Message-Id: <20010617181041.7153C3E0B@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jens Schweikhardt writes: > hello, world\n > > with a system cvsupped June 6th I can reliably reproduce a > [panic] > when I try to unmount a deleted mdconfig device. Here's the recipe: > > # file iso is a Freebsd 4.3 Wind River CD image made with > # dd if=/dev/cd0c of=file.iso bs=2048 > > mdconfig -a -t vnode -f file.iso > mount -t cd9660 /dev/md0 /mnt/freebsd-cd > mdconfig -d -u md0 > umount /dev/md0 > > I'm not sure if this is the right fix but what about having the > mdconfig -d fail with EBUSY in case someone tries to delete a mounted > md device? Been there, done that. Got the patches and long thread(s) to prove it ;-). See message ID 20010313071744.C988C3E09@bazooka.unixfreak.org. > > Regards, > > Jens > -- > Jens Schweikhardt http://www.schweikhardt.net/ > SIGSIG -- signature too long (core dumped) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message