http://qa.mandrakesoft.com/show_bug.cgi?id=3574
------- Additional Comments From [EMAIL PROTECTED] 2003-04-01 09:36 -------
the patch is not yet in any rpm. It needs to be reviewed first and that will
take a while. I might provide unofficially an updated kernel somewhere, but not
before the weekend (no time now).
the no_tray_lock option you add to the fstab entry. The reason is that it is not
supermounts fault that many apps do not close the files properly, so supermount
thinks something is actively using the file and refuses to let you remove it.
However, I found that for readonly devices like cdroms it is usually safe to
remove the drive as all programs i tried can cope more or less gracefully with
the files suddenly disappearing.
There has been some discussion to make it default on readonly devices, but it
makes the code a bit messy, so we probably settle for adding this option to the
default fstab entries created by diskdrake.
Setting this option on writable devices would ofcourse be a very bad idea (it is
the equivalent of removing the floppy when the light is still burning).
d.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
I have all updates applied on stock mdk-9.1 install. I have supermount and
scsi-emulation
enabled.
I have two IDE CD drives:
hdc (scsi-emulated)
hdd (no scsi-emulation).
The CD ejection problem is reproducble for both drives.
Steps to reproduce the problem
---------------------------------------------
1. Put a CD in the drive and close the tray by pressing the CD eject button (the
hardware
button present on the drive). Press the eject button again and verify that the CD is
ejected as
expected. Close the CD tray again.
2. Lets say that the CD drive device is /dev/cdrom (mounted on /mnt/cdrom2). Run the
command:
ls /mnt/cdrom2
Now, press the CD eject button, the CD is ejected fine. Close the CD tray.
3. Run a command to read /dev/cdrom as:
cat /dev/cdrom
4. Wait for the cat command in previous step to end (or you may interrupt the cat
command if
it takes too long).
5. a) Now press the CD eject button. Nothing happens.
b) If I use "eject /dev/cdrom", the CD is ejected fine.
6. a) If I skip step 5b and run "ls /mnt/cdrom2", then the CD files are listed just
fine.
b) After step 6a, if I press the CD eject button, it ejects normally.
This strange behavior is 100% reproducible. It seems that every time the "cat" command
is
used after an "ls" command, it prevents a manual hardware ejection of the CD. After
cat, using
the "ls" command sets things right.
Further investigation revealed that if I manually umount /mnt/cdrom2 then this problem
disappears. If I manually re-mount /mnt/cdrom2, the problem reappears. Obviously,
supermount is not handling things correctly since the problem is related to mounting.
No error messages in dmesg or /var/log/* can be found that explains this odd behavior.
I reported the same bug in bug 2103 but that bug has been marked resolved as "fixed",
even
though the bug still exists in mandrake-9.1 final.
