On Tue, Jul 30, 2013 at 9:58 AM, Thomas Schmitt <scdbac...@gmx.net> wrote:
> Hi, > > Richard Shaw wrote: > > When I use dvd+rw-mediainfo I see > > several different capacaities. Obviously if you use the formatting > > with defect management then you're going to loose some capacity, but > > the output is not clear which one is the correct. > > You probably mean something like this: > > Mounted Media: 41h, BD-R SRM > Media ID: CMCMAG/BA5 > ... > READ FORMAT CAPACITIES: > unformatted: 12219392*2048=25025314816 > 00h(3000): 11826176*2048=24220008448 > 32h(0): 11826176*2048=24220008448 > 32h(0): 5796864*2048=11871977472 > 32h(0): 12088320*2048=24756879360 > > It is an overview of sizes from which you could choose. > 00h and 32h are the Format Codes for the SCSI command FORMAT UNIT. > (3000) is the size of the Spare Area in hexadecimal numbers > counting clusters of 64 KiB. (Cough.) > For some reason my burners report (0) with the format code 32h by > which i could choose a particular payload size. I read different > prescriptions in MMC-5 specs. Shrug. > So the "unformatted" one is pretty obvious which explains my first failure... but then I tried reducing the image using the 24756879360 (24.8GB) size, which still failed. Should I assume then that failure was because growisofs reserved more spare space in its formatting than I allowed for by my image size? If I use 24220008448 when creating my image should my burns always succeed unless I reserve more than a default amount of space for defect management? xorriso would report by > xorriso -outdev /dev/sr0 -list_formats > > a similar list > Format idx 0 : 00h , 11826176s , 23098.0 MiB > Format idx 1 : 32h , 11826176s , 23098.0 MiB > Format idx 2 : 32h , 5796864s , 11322.0 MiB > Format idx 3 : 32h , 12088320s , 23610.0 MiB > > and allow choosing by > xorriso -outdev /dev/sr0 -format by_index_3 > > or > xorriso -outdev /dev/sr0 -format by_size_23610m > Two questions here... First, in reading about xorriso it's really just for ISO formats correct? But in the case of simply formatting the media, we haven't affected the format choice, right? At this point I could still go with ISO9660 or UDF. Second question/problem. When I try xorriso -outdev /dev/sr0 -list_formats I get the following: # xorriso -outdev /dev/sr0 -list_formats GNU xorriso 1.3.0 : RockRidge filesystem manipulator, libburnia project. libburn : SORRY : Cannot open busy device '/dev/sr0' : Device or resource busy libburn : FAILURE : Cannot access '/dev/sr0' as SG_IO CDROM drive xorriso : FAILURE : Cannot aquire drive '/dev/sr0' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' This is as root. As you can see I'm running the latest release. I'm also running 1.3.0 of libburn, libisoburn, libisofs... etc. I am not aware of tools to produce UDF 2.50. mkisofs/genisoimage > create UDF 1.02, afaik. > No, but udftools will create an image up to 2.01, which is what I've been using to format my image files. Thanks, Richard
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
