![]() Metadata is required part of UDF 2.50.Īnd we'd still be missing 2.50/2.60 support in the kernel so still lacking compatibility. So Linux kernel would not be able to modify -R images for sure. I agree it would be nice if it works out of the box.Īlso please note that Linux kernel is not able to write or modify any data on UDF if VAT or Metadata is used or if UDF rev is above 2.01. I will look if there is a way how to mount generated -R disc on Linux by just "loop" module. Hard disks have in most cases 512 bytes long blocks and therefore this value is default for -media-type=hd. Normally also block size is "geometry" information and -media sets it correctly. But as I said, it does not have work with all optical drives and devices. If your purpose is to create -ROM data (you do not want to modify it later after burning to optical media, neither via incremental writing, multisession or real -RW), you can try to choose hard disk type and set correct block size (which is for optical discs 2048). I was reported that there are more devices which really cannot read UDF 2.01 on BD disc. Reason for this is because standards mandates that BD disc must use UDF 2.50 or higher and previous versions do not have to work. media=bdr automatically choose UDF 2.50. So if your purpose is to generate image and then modify, -R is fully unsuitable for you (unless you have a tool which will simulate incremental writing via VAT). There are new options -blocksize=, -startblock=, -lastblock= and -vatblock= which can be used to provide these metainformation if you want to read udf images of optical disc correctly (and not reading directly optical disc). You can look at recent changes in git for udfinfo tool. And without these meta information image itself cannot be read correctly. Optical media provides additional meta information (last written block, table of content, etc.) which are stored "outside" of image itself. It is possible that kernel would not be able to read such "images" if they are not on real optical media. It is just small image which later can be incrementally modified on optical disc. R type differs from all other as it creates UDF image with VAT and it should be "burned" (or packet written) into optical disc. In most cases it would not work (at least correctly). ROM is just read-only without VAT and without spartable (can be used also on -R or -RW medias).Īs -media specify geometry, you cannot use DVD geometry on BDs or CDs. RW is for read-write media with spartable. ![]() Also they are different between -ROM, -R, -RW and -RAM variants of medias.įor example, if you choose -R (as recordable), created UDF image is for (sequential) recording via VAT. And these are different for hard disks, CDs, DVDs and BD. Mkudffs's -media option specify media type, it sets various geometry setting for UDF image. I was looked more deeply on description on your issue and now I see where is the problem. I'm using Debian Buster with udftools 2.1. How else could I write BDR from the command line? It's like I'm missing some critical piece of the inner workings of filesystem images or maybe I'm doing it all wrong. It doesn't work either: "can't read superblock on /dev/loop0" I've thought maybe I should mount specifying the new block size. The new issue is that I can't longer mount the image to copy the files in: "wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error." I'm not using -m bdr because it uses UDF2.50 and I can't write to that image. Mkudffs -m dvdr -b 2048 -l "label" mybdr.udf I've read this issue can be related to the UDF image using 512 bytes sectors and BDR having 2048 bytes sectors. I have to use the loop option to be able to mount it. Now I'm trying the same and the written BDR can't be mounted. After that I loop-mounted the image to copy the data in and I burned to BDR media using growisofs.The command I used was very simple:Īnd evertything worked. I've used mkudffs in the past for creating UDF images.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |