Bug 9474 - files written to an ide zip drive are corrupted
files written to an ide zip drive are corrupted
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2000-02-15 16:58 EST by Jamie Gegerson
Modified: 2014-03-16 22:12 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-15 17:04:42 EST
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 Jamie Gegerson 2000-02-15 16:58:19 EST
I've got an internal IDE zip drive at /dev/hdd and am using:

   * redhat 6.0
   * kernel release 2.2.5-22 (the only thing I've upgraded)
   * a Gateway GP6-400

my fstab has the following related entries:

   * /dev/hdd1    /mnt/lzip    ext2    user,noauto    0    0
   * /dev/hdd4    /mnt/wzip    vfat    user,noauto    0    0

What happens is, I can mount and read a zip disk and everything is fine,
but anything I write to the disk from this system is unusable.
I can't use the files on the system that wrote 'em or anywhere else. The
files also fail a "sum" check:

     [jamieg@test]sum /home/jamieg/bzip2-09.0c.tar.gz
     37468   441
     [jamieg@test]cp /home/jamieg/bzip2-09.0c.tar.gz /mnt/wzip
     [jamieg@test]sum /mnt/wzip/bzip2-09.0c.tar.gz
     16286   441

I upgraded the kernel from 2.2.5-15 to 2.2.5-22 thinking that this might
correct the problem, but there has been no change.
Comment 1 Bill Nottingham 2000-02-15 17:04:59 EST
You need a later kernel, such as the one that shipped with 6.1.
Comment 2 Jamie Gegerson 2000-02-15 17:08:59 EST
What is the latest version of the kernel and where can I get it? I was under the
impression that the rpms I downloaded from redhat today (to go to 2.2.5-22) were
the most recent ones.

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