Bug 786954

Summary: Cannot mount cdroms with 3.2.2-1.fc16
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-06 17:57:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Orion Poplawski 2012-02-02 18:27:58 UTC 
Description of problem:

With 3.2.2-1.fc16 I cannot mount cdroms.  Get messages like:

Feb  2 11:01:43 orca kernel: [ 8802.509921] EXT4-fs (sr0): VFS: Can't find ext4 filesystem
Feb  2 11:01:43 orca kernel: [ 8802.532574] EXT4-fs (sr0): VFS: Can't find ext4 filesystem
Feb  2 11:01:43 orca kernel: [ 8802.553207] EXT4-fs (sr0): VFS: Can't find ext4 filesystem
Feb  2 11:01:43 orca kernel: [ 8802.577246] attempt to access beyond end of device
Feb  2 11:01:43 orca kernel: [ 8802.577253] sr0: rw=0, want=68, limit=4
Feb  2 11:01:43 orca kernel: [ 8802.577258] isofs_fill_super: bread failed, dev=sr0, iso_blknum=
16, block=16
Feb  2 11:01:43 orca kernel: [ 8802.597995] FAT-fs (sr0): bogus number of reserved sectors
Feb  2 11:01:43 orca kernel: [ 8802.598023] FAT-fs (sr0): Can't find a valid FAT filesystem
Feb  2 11:01:43 orca kernel: [ 8802.621603] hfs: can't find a HFS filesystem on dev sr0.
Feb  2 11:01:48 orca kernel: [ 8807.024934] hfs: unable to find HFS+ superblock

Works fine with 3.2.1-3.fc16.i686.PAE
Comment 1 Orion Poplawski 2012-02-02 19:13:23 UTC 
Actually, not that great with 3.2.1-3.  Can mount but accessing some files triggers:

[ 1139.080717] attempt to access beyond end of device
[ 1139.080726] sr0: rw=0, want=390552, limit=174088
[ 1139.080735] attempt to access beyond end of device
[ 1139.080740] sr0: rw=0, want=390496, limit=174088

Same cdrom works fine in a different windows machine.
Comment 2 Dave Jones 2012-02-03 17:19:51 UTC 
this is the only report we've had of this, and it's been fine on multiple systems here. I'm suspecting either bad hardware, or bad media (some drives may tolerate it better than others).
Comment 3 Orion Poplawski 2012-02-06 17:57:29 UTC 
Could be.  Can't reproduce today with 3.2.3-2.