Bug 5472 - pktcdvd avoid to read iso9660 DVDs.
Summary: pktcdvd avoid to read iso9660 DVDs.
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Bartlomiej Zolnierkiewicz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-20 01:36 UTC by SGh
Modified: 2006-05-02 07:15 UTC (History)
0 users

See Also:
Kernel Version: 2.6.13
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description SGh 2005-10-20 01:36:43 UTC
Distribution: Debian 3.1 r0a "Sarge"
Hardware Environment: MB Soltek SL75KAV (VIA KT133A), CPU AMD-K7 (Athlon)
hdc = NEC ND_3520A, hdd = LG CED-8120B

Software Environment: gcc-2.95.3
Problem Description:
I use pktcdvd compiled as a module. So, here is a bug description:

when I do pktsetup for two my drives:
hdc = NEC ND_3520A
hdd = LG CED-8120B

Seems like packet writing work fine, but in some cases, when I mount iso9660 DVD with 
fstab parameters:
/dev/hdc /media/cdrom0 iso9660,udf ro,users,iocharset=koi8-u,noauto  0 0

Media mounted with no errors, dmesg said:

ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A

but when I try to read some files from it I get I/O error, and dmesg said:

Buffer I/O error on device hdc, logical block 2211422
attempt to access beyond end of device
hdc: rw=0, want=8845696, limit=8650112

or just:

hdc: rw=0, want=8840288, limit=8650112
attempt to access beyond end of device

So, I have to umount media, run # pktsetup -d /my/dev and mount media again, and all errors goes away.

P.S. I'm sorry, but I cannot give exact instructions to reproduce this bug, it appear in some cases, maybe it's depend on time sinse I run pktsetup first (little time - no errors, more time(5-10min) - more probability to get an error). And in most cases error appear, when I try to install packages with aptitude (with root account).

P.P.S. Sorry for my bad english, I live in Ukraine, so I do well in ukrainian or russian :)
Comment 1 SGh 2006-05-02 07:15:24 UTC
Seems like in 2.6.16.11 bug is gone.

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