https://bugzilla.kernel.org/show_bug.cgi?id=71981 Roger (rogerx.oss@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rogerx.oss@xxxxxxxxx --- Comment #1 from Roger (rogerx.oss@xxxxxxxxx) --- I'm also seeing the following error within my logs, subsequently causing BD-R (and likely CD/DVD) media to not be able to be mounted, either manually or by using autofs. kernel: isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16 In my case, seems to be due to previous failed growisofs sessions when writing at a higher riskier speeds to (Verbatim 50GB) dual layer BD-R media, but within drive & media manufacturer's recommendations. The BD-R drive I'm using, LG WH16NS60 displays both this dual layer write problem and subsequent reading problems. The previous LG WH14NS40 BD-R drive, displayed the similar scenario but I did not catch the scsi/kernel error within logs. Either rebooting and/or using the media within a Windows or secondary computer, the media can be read. The above error seems to be caused by: # mount -t iso9660 /dev/sr0 /mnt/tmp mount: /mnt/tmp1: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program, or other error. 32 :-( WORKAROUND SOFT RESET SCSI BUS https://zedt.eu/tech/linux/soft-resetting-sata-devices-linux/ Get host number: # readlink /sys/block/sdX ../devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0/block/sr0 Trigger device delete: # echo 1 > /sys/block/sdX/device/delete Trigger device scan on host controller number as specified above: # echo "- - -" > /sys/class/scsi_host/host1/scan Long story short, this looks like a kernel/growisofs problem. Growisofs is having difficulties writing dual layer (Verbatim) bluray (BD-R) media at speeds above speed=1 here. An error condition is likely incurred, either or both the kernel or growisofs is having problems properly handling. The writing problem is also experienced under MS Windows 10, due to likely MS Windows 10 using max speed. Not known if MS Windows 10 is also have problems with reading after scsi bus errors as described above, etc. -- You are receiving this mail because: You are watching the assignee of the bug.
