Not looking for solutions, just delivering a bug report. I have a 30GB Seagate with one partition on it formatted ReiserFS (version 3.6.25 apparently) on which some CDROM images reside. Kernel 2.4.18 (mandrake).
When I try to read the files I get the following type of messages in my syslog: Aug 20 19:28:28 stroke kernel: attempt to access beyond end of device Aug 20 19:28:28 stroke kernel: 16:41: rw=0, want=471759240, (=0x1c1e7988), limit=471759240 Aug 20 19:33:57 stroke kernel: attempt to access beyond end of device Aug 20 19:33:57 stroke kernel: 16:41: rw=0, want=623828640, (=0x252edea0), limit=623828640 Aug 20 19:36:19 stroke kernel: attempt to access beyond end of device Aug 20 19:36:19 stroke kernel: 16:41: rw=0, want=1685807688, (=0x647b6248), limit=1685807688 Aug 21 00:33:34 stroke kernel: attempt to access beyond end of device Aug 21 00:33:34 stroke kernel: 16:41: rw=0, want=1758259028, (=0x68cce754), limit=1758259028 Aug 21 00:33:38 stroke kernel: attempt to access beyond end of device Aug 21 00:33:38 stroke kernel: 16:41: rw=0, want=389077160, (=0x1730d8a8), limit=389077160 Aug 21 00:33:46 stroke kernel: attempt to access beyond end of device Aug 21 00:33:46 stroke kernel: 16:41: rw=0, want=1411977092, (=0x54290f84), limit=1411977092 I've tried all manor of reiserfscking repeatedly. Each time it seems to fix something different. I've read about the issues with fdisk and not rebooting and admit that this _could_ be my issue but that doesn't explain why all the "want" and "limit" numbers are identical. I'm also curious why upon umount/mounting the partition the location where the read fails changes. I was able to retreive my data but I couldn't tell you why it worked. To do so, I umount/mount'd the partition then cat'd the iso file to /dev/null. THEN I was able to cat the files and redirect them to new files on a different disk. If I try to "copy" 2 files in a row without a umount/mount I get the I/O errors right away. A plain old 'cp' never worked right. Had to do the cat trick for every file. Hope this helps. Lemme know if you want more data. BTW, that problem with the fdisk and not rebooting... Is there any way you can code reiserfsck so it will tell you that you screwed it up? How can I know if I did it right or not at this point? -Frank Johnson -- Nobody snuggles with Max Power. You strap yourself in and feel the "G"s!
