Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, Dima Dorfman writes:
> >Jens Schweikhardt <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
> The idea here is that md(4) should be able to simulate a media which
> disappears with no warning so that people can debug problems related
> to (too) dynamic media transitions.

Right.  I agree with your assessment in the thread I mentioned above.
My apologies if I made it sound derogatory.

> If people think this is too much of a panic(8) implementation we
> can hide this behaviour behind a -JUSTDOIT! option.

This is easy to do; just add an -f option to mdconfig (which can be
converted into an MD_FORCE flag or something) which means "bypass as
many sanity checks as possible".  I'll do the work if it's desired.


                                        Dima Dorfman
                                        [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to