Re: Burning and mounting written BDs

[Kjetil Kjernsmo]

Hi! 

Happy new year, and sorry for my ping times. It took a while to get back to 
recording those discs, but to start off, I have now complete the backups I 
wanted. :-) 

On mandag 1. januar 2024 09:55:26 CET Thomas Schmitt wrote:
> Other than stated yesterday, -for_backup was not the only possible way to
> trigger that bug. If experiments show it even without -for_backup, then
> this does not disprove the theory that you lost a BD-R DL to this bug.
> (Grrr ... i should have remembered and warned.)

Oh, don't worry, I very much appreciate the efforts you've made into this 
software, and that doesn't detract from that! 

> So in any case please try whether xorriso-1.5.6 works better for you.

Yup, I now have 1.5.6 running. I basically did what you detailed, with some 
modifications:


>     cd "$HOME"

I put it into /usr/local/src instead.

>     ./configure --prefix=/usr

and there, I used the /usr/local prefix instead. I prefer to let Debian manage 
/usr.

>     make
> 
> 3: Test the result for willingness to run:
> 
>     ./xorriso/xorriso -version
> 
>   should say:
> 
>     GNU xorriso 1.5.6 : RockRidge filesystem manipulator, libburnia project.
> 
>   Running the installed xorriso should still tell version 1.5.4:
>     xorriso -version

Yup, check.

> 4: Now test whether version 1.5.6 does a better job with your input
> 
>     "$HOME"/xorriso_dir/xorriso-1.5.6/xorriso/xorriso \
>        -outdev "stdio:/dev/null" \
>        -for-backup \
>        -blank as_needed \
>        -speed 4b \
>        --map ./bildebackup-2023/ /Bilder \

Yeah, that worked too (though, it was some other data I wrote)

> 
> If this runs without the error message about "Calculated/written"
> addresses, then you may either make another test with a data file as
> output, like
>     -outdev "$HOME"/bildebackup.iso
> and mount this data file afterwards:
> 
>     sudo mount "$HOME"/bildebackup.iso /mnt/test/

Check.

At this point, I went make install and asked apt to remove the debian 
packages, and then reran the image building.

> Or you may try a real burn run with
>     -outdev /dev/sr0
> and the trailing tray dance commands
>     -commit -eject all -outdev /dev/sr0

Yeah, and then I did that from the code installed in /usr/local, and that 
worked too!

> Reason for long directory records and thus for multiple CE blocks per
> directory can be peculiarities of the metadata of the input files:
> - Long file names

Right, it is likely I have those.

Anyway, for completeness, I then went back to the discs I had given up, to see 
if I might be able to find more error messages in the logs when I mounted them. 
And to me my great surprise, they all mounted without a hitch! Which could 
indicate the drive was a bit weird...?

Kind regards,

Kjetil