https://bugzilla.kernel.org/show_bug.cgi?id=13602 Bill McGonigle <bill-osdl.org-bugzilla@xxxxxxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Kernel Version|2.6.29.4-167.fc11.i586 |2.6.34.7-56.fc13.x86_64 --- Comment #5 from Bill McGonigle <bill-osdl.org-bugzilla@xxxxxxxxxxxxxxxx> 2010-10-28 16:40:30 --- @Christoph: good workaround. I can losetup my /dev/sr0 and mount the discs (tested 1 anyway). I need to omit the session=1 option on the loopback but it does mount that way. Just to be sure, I confirmed sr0 won't mount without the session option. Not sure what would happen if the data were on session=2. For the HFS vs. SCSI question, I'm not clear why 22 out of 25 discs in this set work OK but the remaining 3 would not. They're factory-stamped discs, no idea how they were mastered. The only dmesg I get is: hfs: unable to set blocksize to 512 hfs: can't find a HFS filesystem on dev sr0. This is now kernel 2.6.34.7-56.fc13.x86_64. Not sure if it's helpful, but here are the /sys sizes: [bfccomputing@zpm sr0]$ more `pwd`/queue/*size :::::::::::::: /sys/block/sr0/queue/hw_sector_size :::::::::::::: 2048 :::::::::::::: /sys/block/sr0/queue/logical_block_size :::::::::::::: 2048 :::::::::::::: /sys/block/sr0/queue/max_segment_size :::::::::::::: 65536 :::::::::::::: /sys/block/sr0/queue/minimum_io_size :::::::::::::: 2048 :::::::::::::: /sys/block/sr0/queue/optimal_io_size :::::::::::::: 0 :::::::::::::: /sys/block/sr0/queue/physical_block_size :::::::::::::: 2048 I can't even say this is a feature implemented in MacOSX for compatibility that linux lacks - for all I know, they do some sort of loopback mount automagically if certain kinds of discs are detected. I don't know if there are any linux equivalents for doing something similar by the kernel; one could imagine userland machinations that could do the right thing, though perhaps costly. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
