Bug 3072
Summary: | ATAPI Zip drive doesn't work properly | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | David Flater (purl) |
Component: | IDE | Assignee: | io_ide (io_ide) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | bp, bunk, dave, devzero, htejun, protasnb |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.7 et seq. - 2.6.21.5-smp | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
David Flater
2004-07-15 08:04:31 UTC
Happy one year bug anniversary! I am now running kernel.org kernel version 2.6.12.2 on a completely different machine within a clean install of Slackware 10.1 and the bug reproduces same as always. ide-floppy driver 0.99.newide hdc: No disk in drive hdc: 98304kB, 32/64/96 CHS, 4096 kBps, 512 sector size, 2941 rpm Linux version 2.6.12.2 (dave@yellowbeard) (gcc version 3.3.4) #1 SMP Sat Jul 9 17:42:32 EDT 2005 bash-3.00# mke2fs -m 0 /dev/hdc4 mke2fs 1.35 (28-Feb-2004) mke2fs: No such device or address while trying to determine filesystem size Syslog says: Jul 17 19:52:35 yellowbeard kernel: hdc: 98304kB, 196608 blocks, 512 sector size If I repeat the mke2fs command without ejecting the disk, it works on the second try. This problem does not occur with the 2.4.x kernel series. Thank you. Is this issue still present in kernel 2.6.17? Happy two year bug anniversary. As of now I can't even mount a disk on the first try. I'm a little vague on what happened to the kernel between 2.4 and 2.6 and whether it's all udev's fault, but my problems are certainly consistent with the (WILL_NOT_FIX) regression discussed in the udev thread archived at http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=407950;page=1;sb=post_latest_reply;so=ASC;mh=25;list=linux FWIW I am still not running udevd. bash-3.1$ cat /proc/version Linux version 2.6.17.4 (root@yellowbeard) (gcc version 3.4.6) #2 SMP PREEMPT Thu Aug 3 21:25:34 EDT 2006 bash-3.1$ dmesg | fgrep ZIP hdc: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive hdd: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive bash-3.1$ ls -al /dev/hdd brw-rw---- 1 root disk 22, 64 2002-06-09 15:27 /dev/hdd bash-3.1$ ls -al /dev/hdd? brw-rw---- 1 root disk 22, 65 2002-06-09 15:27 /dev/hdd1 brw-rw---- 1 root disk 22, 66 2002-06-09 15:27 /dev/hdd2 brw-rw---- 1 root disk 22, 67 2002-06-09 15:27 /dev/hdd3 brw-rw---- 1 root disk 22, 68 2002-06-09 15:27 /dev/hdd4 brw-rw---- 1 root disk 22, 69 2002-06-09 15:27 /dev/hdd5 brw-rw---- 1 root disk 22, 70 2002-06-09 15:27 /dev/hdd6 brw-rw---- 1 root disk 22, 71 2002-06-09 15:27 /dev/hdd7 brw-rw---- 1 root disk 22, 72 2002-06-09 15:27 /dev/hdd8 brw-rw---- 1 root disk 22, 73 2002-06-09 15:27 /dev/hdd9 [ put disk in hdd, wait for drive to spin up and for light to stop blinking ] bash-3.1# mount -t vfat /dev/hdd4 /mnt mount: /dev/hdd4 is not a valid block device Syslog: Aug 17 19:39:51 yellowbeard kernel: hdd: The disk reports a capacity of 250640384 bytes, but the drive only handles 250609664 Aug 17 19:39:51 yellowbeard kernel: hdd: 244766kB, 489532 blocks, 512 sector size bash-3.1# mount -t vfat /dev/hdd4 /mnt Syslog: Aug 17 19:41:48 yellowbeard kernel: hdd: The disk reports a capacity of 250640384 bytes, but the drive only handles 250609664 Aug 17 19:41:49 yellowbeard kernel: hdd: hdd4 bash-3.1# ls -al /mnt total 109816 drwxr-xr-x 2 root root 16384 1969-12-31 19:00 . drwxr-xr-x 21 root root 4096 2006-08-03 20:56 .. -rwxr-xr-x 1 root root 112427692 2006-07-11 20:43 xp_backup.tar.gz OK, is this a three year bug now? Is the bug still there with recent kernels? Thanks. It's still there. Now running Slackware 12.0 "huge smp" kernel and udev. bash-3.1$ cat /proc/version Linux version 2.6.21.5-smp (root@midas) (gcc version 4.1.2) #2 SMP Tue Jun 19 14:58:11 CDT 2007 bash-3.1$ ps -ef | fgrep udev root 1114 1 0 17:47 ? 00:00:00 /sbin/udevd --daemon bash-3.1$ udevd --version 111 bash-3.1$ dmesg | fgrep ZIP hdc: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive bash-3.1$ ls -al /dev/hdc* brw-rw---- 1 root plugdev 22, 0 2007-09-04 13:47 /dev/hdc [Insert a vfat Zip disk, wait 10 seconds] bash-3.1# mount -t vfat /dev/hdc4 /mnt mount: special device /dev/hdc4 does not exist bash-3.1# mount -t vfat /dev/hdc4 /mnt mount: special device /dev/hdc4 does not exist [Hmmm...] bash-3.1# dd if=/dev/hdc of=/dev/null bs=512 count=1 1+0 records in 1+0 records out 512 bytes (512 B) copied, 0.00567736 s, 90.2 kB/s > Sep 4 17:54:09 yellowbeard kernel: hdc: 244766kB, 489532 blocks, 512 sector > size > Sep 4 17:54:09 yellowbeard kernel: hdc: The disk reports a capacity of > 250640384 bytes, but the drive only handles 250609664 > Sep 4 17:54:10 yellowbeard kernel: hdc: hdc4 bash-3.1# ls -al /dev/hdc* brw-rw---- 1 root plugdev 22, 0 2007-09-04 13:47 /dev/hdc brw-rw---- 1 root plugdev 22, 4 2007-09-04 17:54 /dev/hdc4 bash-3.1# mount -t vfat /dev/hdc4 /mnt [Success] [Unmount, eject disk] bash-3.1# ls -al /dev/hdc* brw-rw---- 1 root plugdev 22, 0 2007-09-04 13:47 /dev/hdc brw-rw---- 1 root plugdev 22, 4 2007-09-04 17:56 /dev/hdc4 bash-3.1# mount -t vfat /dev/hdc4 /mnt mount: /dev/hdc4: can't read superblock > Sep 4 17:58:48 yellowbeard kernel: hdc: No disk in drive [Insert a vfat Zip disk, wait 10 seconds] bash-3.1# mount -t vfat /dev/hdc4 /mnt [Success] [Unmount, change disks] bash-3.1# fdisk /dev/hdc [... edit partition table ...] Command (m for help): p Disk /dev/hdc: 100 MB, 100663296 bytes 64 heads, 32 sectors/track, 96 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 50 51184 83 Linux /dev/hdc2 51 96 47104 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. bash-3.1# ls -al /dev/hdc* brw-rw---- 1 root plugdev 22, 0 2007-09-04 18:05 /dev/hdc brw-rw---- 1 root plugdev 22, 1 2007-09-04 18:05 /dev/hdc1 brw-rw---- 1 root plugdev 22, 2 2007-09-04 18:05 /dev/hdc2 bash-3.1# mke2fs /dev/hdc1 [Success] [Eject disk] [Insert original vfat disk] bash-3.1# ls -al /dev/hdc* brw-rw---- 1 root plugdev 22, 0 2007-09-04 18:05 /dev/hdc brw-rw---- 1 root plugdev 22, 1 2007-09-04 18:07 /dev/hdc1 brw-rw---- 1 root plugdev 22, 2 2007-09-04 18:07 /dev/hdc2 bash-3.1# mount -t vfat /dev/hdc4 /mnt mount: special device /dev/hdc4 does not exist bash-3.1# dd if=/dev/hdc of=/dev/null bs=512 count=1 1+0 records in 1+0 records out 512 bytes (512 B) copied, 0.0055659 s, 92.0 kB/s bash-3.1# mount -t vfat /dev/hdc4 /mnt [Success] bash-3.1# ls -al /dev/hdc* brw-rw---- 1 root plugdev 22, 0 2007-09-04 18:05 /dev/hdc brw-rw---- 1 root plugdev 22, 4 2007-09-04 18:09 /dev/hdc4 This bug will have to be submitted to linux-ide I guess. Is this still a problem with recent kernels? Yes.... Reconfirmed with 2.6.24.2 mainline. With 2.6.24.3 I determined that if the "stable" IDE drivers under ATA/ATAPI/MFM/RLL support are disabled, the Zip drive works great with the "experimental" PATA drivers in libata. This is probably what needs to be used anyway, I think the bug is resolved with new drivers working. Not the case here, reopening the bug. David, would you please test 2.6.25 to see whether the bug persists. See, since .24 a lot of stuff got removed from the driver and before we do any debugging I'd like to know the bug is still there :). Thanks. I guess that we should close this bug for now. |