In message <[EMAIL PROTECTED]>, Dima Dorfman write
s:
>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.
If people think this is too much of a panic(8) implementation we
can hide this behaviour behind a -JUSTDOIT! option.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
