Summary: | Garbled DOS floppy listings ( 9.4 GB in all !!! ) which also cause problems in KDE 3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aniruddha Shankar <k> |
Component: | [OLD] Unspecified | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | styx, vapier |
Priority: | High | ||
Version: | 1.1a | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aniruddha Shankar
2002-06-03 07:43:09 UTC
More information at http://bugs.kde.org/db/41/41685.html since you managed to track the problem down to kde, why did you post the bug for gentoo ? also, did you try mounting the floppy on a diff linux machine to see if you got the same results ? floppies are far from reliable, ever kde's just the wm that some users happen to use. the problem is present in all environments, including a text-only one. It's just that the problem is aggravated when using kde. And yes, the floppy, when mounted on another linux system (I have about 20 identical systems here running Gentoo 1.1a) gives me the same error. The same floppy, when mounted on a windows machine works without errors. I have yet to try it on a linux machine from another distribution, but shall do so and report asap. Aniruddha Karim Shankar Bangalore, India Can you reproduce this with other floppies you know are OK? I've gotten an old 800MB disk to be reported as 1.19TB once, so AFAICS, this could be a physical problem with the floppy, or a generic linux floppy support problem. The fact that Windows can read the floppy without problems is of course a bit disturbing, but I wouldn't use that as an insurance that the floppy is OK. The mysterious floppy bug (a.k.a. the drive Karim gibbering mad bug) was sighted just now. Present was floppy with strange files full of questionmarks and garbled files (sizes way way above 1.44 mb). It was taken to a Windows 2000 5.00.2195 (Service Pack 2) machine. No garbled characters in listing, also, no problems copying a file from the floppy. It was error checked with scandisk with the "automatically fix file system errors" and "scan for and attempt recovery of bad sectors" options checked. After scandisk, no garbled files in the listing under Linux, no problems mounting and unmounting at all. I am trying to get hold of a disk utility which will tell me more about what problems are on the disk. the dosfsck from dosfstools is broken, will not check floppies for bad clusters unless the floppy is empty. cheers... Am unable to reproduce this error, though, to tell the truth, havent tried (and dont have the faintest idea how to). aniruddha, what's the latest on this? twentyfive karim # ls -lh /floppy <=== mounted as vfat ls: /floppy/iskette.: No such file or directory ls: /03/98 w.yx: No such file or directory total 251M dr-xr-xr-x 0 root root 512 Aug 14 2001 >???g???.?o? -rwxr-xr-x 1 root root 104K Aug 31 2001 IPissuesinM_A.doc -rwxr-xr-x 1 root root 61K Dec 31 13:32 conver.doc -rwxr-xr-x 1 root root 71K Oct 19 2001 employee ip non competition.doc -rwxr-xr-x 1 root root 109K Oct 19 2001 employmentissuesinM_A_s.doc -rwxr-xr-x 1 root root 86K Oct 19 2001 envpolicy1.doc -rwxr-xr-x 1 root root 90K Oct 19 2001 envpolicy2.doc -rwxr-xr-x 1 root root 144K Oct 19 2001 ~WRL2787.tmp -rwxr-xr-x 1 root root 109K Oct 19 2001 ~WRL3540.tmp -r-xr-xr-x 1 root root 14M Jan 17 07:16 ?z?t7???.?i? -rwxr-xr-x 1 root root 0 Jan 1 1980 ?? dr-xr-xr-x 118 root root 54K May 23 1982 ???z?t??.??? dr-xr-xr-x 0 root root 512 Jan 2 2024 ?q?.??q -rwxr-xr-x 1 root root 0 Jan 19 1980 ?>?*=47).ihc -rwxr-xr-x 1 root root 235M Dec 20 1929 ?3????.??? twentyfive karim # umount /floppy twentyfive karim # mount -t msdos /dev/fd0 /floppy twentyfive karim # ls -lh /floppy ls: /floppy/ twentyfive karim # ls -lh /floppy <=== mounted as vfat ls: /floppy/iskette.: No such file or directory ls: /03/98 w.yx: No such file or directory total 251M dr-xr-xr-x 0 root root 512 Aug 14 2001 >???g???.?o? -rwxr-xr-x 1 root root 104K Aug 31 2001 IPissuesinM_A.doc -rwxr-xr-x 1 root root 61K Dec 31 13:32 conver.doc -rwxr-xr-x 1 root root 71K Oct 19 2001 employee ip non competition.doc -rwxr-xr-x 1 root root 109K Oct 19 2001 employmentissuesinM_A_s.doc -rwxr-xr-x 1 root root 86K Oct 19 2001 envpolicy1.doc -rwxr-xr-x 1 root root 90K Oct 19 2001 envpolicy2.doc -rwxr-xr-x 1 root root 144K Oct 19 2001 ~WRL2787.tmp -rwxr-xr-x 1 root root 109K Oct 19 2001 ~WRL3540.tmp -r-xr-xr-x 1 root root 14M Jan 17 07:16 ?z?t7???.?i? -rwxr-xr-x 1 root root 0 Jan 1 1980 ?? dr-xr-xr-x 118 root root 54K May 23 1982 ???z?t??.??? dr-xr-xr-x 0 root root 512 Jan 2 2024 ?q?.??q -rwxr-xr-x 1 root root 0 Jan 19 1980 ?>?*=47).ihc -rwxr-xr-x 1 root root 235M Dec 20 1929 ?3????.??? twentyfive karim # umount /floppy twentyfive karim # mount -t msdos /dev/fd0 /floppy twentyfive karim # ls -lh /floppy ls: /floppy/ë>*=47).ihc: No such file or directory ls: /floppy/ú3Àм.Ø: No such file or directory ls: /floppy/»: No such file or directory ls: /floppy/iskette.: No such file or directory [clipped for brevity, mounting as msdos instead of vfat still shows errors] twentyfive karim # umount /floppy twentyfive karim # mdir a: <=== strangely enough, this works fine. Volume in drive A has no label Directory for A:/ EMPLOY~2 DOC 73216 10-19-2001 10:00 employee ip non competition.doc IPISSU~1 DOC 106496 08-31-2001 19:26 IPissuesinM_A.doc ENVPOL~1 DOC 88576 10-19-2001 10:01 envpolicy1.doc ENVPOL~2 DOC 92672 10-19-2001 10:01 envpolicy2.doc EMPLOY~1 DOC 112128 10-19-2001 10:01 employmentissuesinM_A_s.doc conver doc 62464 12-31-2001 13:32 6 files 535 552 bytes 662 528 bytes free At this stage, I created a raw copy of the disk using twentyfive karim # dd if=/dev/fd0 of=culprit I ddd this image onto a new floppy and verified that the errors in the listings appeared when mounted in vfat and msdos mode. As before, mtools' mdir was able to read the floppy perfectly. This image of the floppy has been uploaded at https://mail.nls.ac.in/floppymadness/ along with it's md5. Dosfsck from dosfstools was able to rectify the errors on the floppy, the output is shown below: twentyfive karim # dosfsck -waft /dev/fd0 <==== log of this is at https://mail.nls.ac.in/floppymadness/dosfsck.log dosfsck 2.8, 28 Feb 2001, FAT32, LFN /ë>\220*=47).IHC Bad file name. Auto-renaming it. Renamed to FSCK0000.REN [clipped for brevity] Performing changes. /dev/fd0: 22 files, 1553/2847 clusters twentyfive karim # mount /floppy twentyfive karim # ls -lh /floppy total 777K -rwxr-xr-x 1 root root 104K Aug 31 2001 IPissuesinM_A.doc -rwxr-xr-x 1 root root 61K Dec 31 13:32 conver.doc -rwxr-xr-x 1 root root 71K Oct 19 2001 employee ip non competition.doc -rwxr-xr-x 1 root root 109K Oct 19 2001 employmentissuesinM_A_s.doc -rwxr-xr-x 1 root root 86K Oct 19 2001 envpolicy1.doc -rwxr-xr-x 1 root root 90K Oct 19 2001 envpolicy2.doc -rwxr-xr-x 1 root root 0 Jan 19 1980 fsck0000.ren -rwxr-xr-x 1 root root 0 Dec 20 1929 fsck0001.ren -rwxr-xr-x 1 root root 0 Jan 1 1980 fsck0002.ren dr-xr-xr-x 0 root root 0 Mar 20 1996 fsck0003.ren -r-xr-xr-x 1 root root 0 Jan 17 07:16 fsck0004.ren dr-xr-xr-x 0 root root 0 Jan 2 2024 fsck0005.ren dr-xr-xr-x 0 root root 0 Aug 14 2001 fsck0006.ren dr-xr-xr-x 0 root root 0 May 23 1982 fsck0007.ren -rwxr-xr-x 1 root root 0 Jan 1 1980 fsck0008.ren -rwxr-xr-x 1 root root 144K Oct 19 2001 ~WRL2787.tmp -rwxr-xr-x 1 root root 109K Oct 19 2001 ~WRL3540.tmp twentyfive karim # umount /floppy twentyfive karim # mount -t msdos /dev/fd0 /floppy twentyfive karim # ls -lh /floppy total 777K -rwxr-xr-x 1 root root 61K Dec 31 13:32 conver.doc -rwxr-xr-x 1 root root 109K Oct 19 2001 employ~1.doc -rwxr-xr-x 1 root root 71K Oct 19 2001 employ~2.doc -rwxr-xr-x 1 root root 86K Oct 19 2001 envpol~1.doc -rwxr-xr-x 1 root root 90K Oct 19 2001 envpol~2.doc -rwxr-xr-x 1 root root 0 Jan 19 1980 fsck0000.ren -rwxr-xr-x 1 root root 0 Dec 20 1929 fsck0001.ren -rwxr-xr-x 1 root root 0 Jan 1 1980 fsck0002.ren dr-xr-xr-x 0 root root 0 Mar 20 1996 fsck0003.ren -r-xr-xr-x 1 root root 0 Jan 17 07:16 fsck0004.ren dr-xr-xr-x 0 root root 0 Jan 2 2024 fsck0005.ren dr-xr-xr-x 0 root root 0 Aug 14 2001 fsck0006.ren dr-xr-xr-x 0 root root 0 May 23 1982 fsck0007.ren -rwxr-xr-x 1 root root 0 Jan 1 1980 fsck0008.ren -rwxr-xr-x 1 root root 104K Aug 31 2001 ipissu~1.doc -rwxr-xr-x 1 root root 144K Oct 19 2001 ~wrl2787.tmp -rwxr-xr-x 1 root root 109K Oct 19 2001 ~wrl3540.tmp Please dd the image onto your floppies and check them to your hearts' content. I do not have access to any system not running 2.4.19-gentoo-r7 and would be grateful if someone were to check if this error appears with different kernels. regards, Aniruddha Shankar Bangalore, India looks like dosfsck worked then? If dosfsck worked reliably then I wouldnt really have a problem. It doesnt, however. If there is a file on the floppy which is on an area of the disk that has a bad block, dosfsck aborts without fixing the error or any errors on subsequent files. mbadblocks aborts without marking any blocks as bad as well. I'll post logs of this if anyone needs it. thanks a million, people... Aniruddha Shankar Bangalore, India ive seen this kind of thing before using vfat on regular drives (not gentoo specific) basically it means that vfat support isnt perfect and as such bugs in the kern probably need to be ironed out (which means i'm closing this bug) |