From owner-freebsd-stable Fri Dec 28 9:51:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by hub.freebsd.org (Postfix) with ESMTP id BDAE437B41A for ; Fri, 28 Dec 2001 09:51:26 -0800 (PST) Received: from jamestown.21stcentury.net (24-148-18-116.na.21stcentury.net [24.148.18.116]) by smtp-2.enteract.com (Postfix) with ESMTP id 43CCB6174; Fri, 28 Dec 2001 11:51:26 -0600 (CST) Received: (from jtm@localhost) by jamestown.21stcentury.net (8.11.6/8.11.3) id fBSHowe00674; Fri, 28 Dec 2001 11:50:59 -0600 (CST) (envelope-from jtm63@enteract.com) X-Authentication-Warning: jamestown.21stcentury.net: jtm set sender to jtm63@enteract.com using -f To: freebsd-stable@freebsd.org Subject: CR-RW not locked when mounted From: James McNaughton Date: 28 Dec 2001 11:50:57 -0600 Message-ID: <86d70zb5dq.fsf@jamestown.21stcentury.net> Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= In the past, when I had mounted a CD-R/RW/ROM on my SCSI CD-RW drive, the drive door was locked until I umounted the thing. Today, I found that this isn't working as it did. I wrote a CD-RW yesterday and then mounted the file system to make certain I had everthing I wanted. Then today -- having forgotten that I had a file system mounted -- hit the eject button on the CD-RW and changed the disk. I then found that I couldn't mount the new disk since the device (/dev/cd0c) was busy. I tried to umount the file system and was told the device was busy. I replaced the original disk and tried again with the same result. I tried 'umount -f' with no success. I eventually rebooted the machine to single user, ran fsck which found an unreferenced directory in the root file system. Now, everything is back to normal. However, it seems the wole episode shouldn't have happened. Could this be a recently introduced bug? Any ideas? INFO to FOLLOW: --=-=-= Content-Disposition: attachment; filename=junk.txt Content-Description: uname and dmesg output FreeBSD jamestown.21stcentury.net 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Dec 12 07:02:38 CST 2001 root@jamestown.21stcentury.net:/usr/obj/usr/src/sys/JAMESTOWN_II i386 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Wed Dec 12 07:02:38 CST 2001 root@jamestown.21stcentury.net:/usr/obj/usr/src/sys/JAMESTOWN_II Timecounter "i8254" frequency 1193182 Hz CPU: Overdrive Pentium/P55C (180.41-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x1543 Stepping = 3 Features=0x8001bf real memory = 67108864 (65536K bytes) config> q avail memory = 61550592 (60108K bytes) Preloaded elf kernel "kernel" at 0xc03ba000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03ba0a8. Preloaded splash_image_data "/boot/splash.bmp" at 0xc03ba0f8. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Using $PIR table, 4 entries at 0xc00f99e0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ign0 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at 6.0 irq 11 atapci0: port 0xfce0-0xfcff,0xf8dc-0xf8df,0xfcd0-0xfcd7,0xfcdc-0xfcdf,0xfcc8-0xfccf irq 14 at device 14.0 on pci0 ata2: at 0xfcc8 on atapci0 ata3: at 0xfcd0 on atapci0 isa0: too many dependant configs (8) orm0: