Bug 38871 - kernel 2.4.2-2 does not lock zip drive when mounted
kernel 2.4.2-2 does not lock zip drive when mounted
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
: 37072 41804 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2001-05-02 20:53 EDT by Carlos Rodrigues
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-06-25 16:54:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Carlos Rodrigues 2001-05-02 20:53:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686)

After mounting a zip drive the disk doesn't get locked in the drive, I can
eject it without unmounting.

Reproducible: Always
Steps to Reproduce:
1. insert zip disk in drive
2. mount it
3. press eject

Actual Results:  The disk pops out.

Expected Results:  The disk should of stayed inside until unmount.
Comment 1 Arjan van de Ven 2001-05-03 03:58:45 EDT
Can you try disabling "magicdev" and/or "autorun" in the Control Center?
This program tends to cause this kind of behavior.

Comment 2 Carlos Rodrigues 2001-05-03 17:59:10 EDT
Both magicdev and autorun are disabled.

I forgot to mention that the drive is a zip 100 plus connected to a ISA Iomega
Zoom SCSI card.
Comment 3 Tim Lundstrvm 2001-05-04 03:20:15 EDT
The same goes for the paralell port Zip-drive with ppa-module
Comment 4 Alan Cox 2001-05-28 13:57:57 EDT
*** Bug 41804 has been marked as a duplicate of this bug. ***
Comment 5 Alan Cox 2001-05-28 13:59:28 EDT
*** Bug 37072 has been marked as a duplicate of this bug. ***
Comment 6 Carlos Rodrigues 2001-06-25 16:54:43 EDT
For me, kernel 2.4.3-12 from updates.redhat.com fixes this problem.

Note You need to log in before you can comment on or make changes to this bug.