http://qa.mandrakesoft.com/show_bug.cgi?id=5981
Product: kernel
Component: program
Summary: supermount failure for bad cdrom
Product: kernel
Version: 2.4.22-10mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: program
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
If I try to mount bad cdrom's with via supermount, I have a very strange effect
in /mnt.
here's what I do:
1. insert bad cd
2. % mount
[...]
none on /mnt/floppy type supermount
(rw,sync,dev=/dev/fd0,fs=auto,--,iocharset=utf8,umask=0)
none on /mnt/cdrom type supermount
(ro,dev=/dev/scd0,fs=auto,--,iocharset=utf8,umask=0)
[...]
3. % cd /mnt
4. % ls -la
drwxr-xr-x 7 root root 4096 Sep 21 23:08 ./
drwxr-xr-x 21 root root 4096 Sep 26 08:35 ../
drwxrwxrwx 0 root root 0 Sep 26 12:23 cdrom/
drwxrwxrwx 0 root root 0 Sep 26 08:35 floppy/
5. % ls -la cdrom
-bash: cd: cdrom/: Input/output error
6. % ls -la cdrom/
ls: cdrom/: Not a directory
7. % ls -la
drwxr-xr-x 7 root root 4096 Sep 21 23:08 ./
drwxr-xr-x 21 root root 4096 Sep 26 08:35 ../
drwxr-xr-x 2 root root 4096 Sep 7 19:25 camera/
---------- 1 root root 0 Sep 26 12:23 cdrom
8. % rm -rf cdrom
rm: remove.c:995: remove_dir: Assertion `saved_errno == 1' failed.
Aborted (core dumped)
... what has happened to my cdrom directory?
Workaround is to umount /mnt/cdrom and mount it again.
The system is in sync with current cooker and no manual modifications in
/etc/fstab (if that matters).
and another comment: bugzilla has 2.4.22-3 as current kernel, though there is a
2.4.22-10 in the list ...
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
