--- Comment #27 from Thomas Schmitt <scdbac...@gmx.net> ---
grrr. The waste of your BD-R is to blame on libburn's automatic decision
to handle this burn under the SAO/DAO model: Known track size, as much
write preparations in advance as possible.
After the preparations are done, it makes no sense to abort the burn.
With CD media the burner would get stuck. With BD-R the track would
already be reserved but not written.
The medium whould have been saved by the explicit cdrskin option -tao.
In this case no writing would have happened if the error already occurs
at the first read attempt on the input file.
Even better would have been option -waiti with data comming from stdin:
cdrskin -v dev=/dev/sr0 fs=32m -eject -waiti - <image.udf
which would not have touched the drive at all, if no data were available.
Sorry again. I should have proposed the most rugged variant.
My question about the hex editor is obsolete now.
I see in the cdrskin log the message that no input bytes were read:
Track 01: Total bytes read/written: 0/49199448064 (24023168 sectors).
But the reason for the error 22 on read(2) has still to be found.
Have a nice day :)
You are receiving this mail because:
You are watching all bug changes.