Re: First case, check if wodim reliably spoils the optical media

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

> I don't see any benefit from trying to "fix" wodim.

I do not try to fix wodim. I try to find out why it fails.
If we come to a conclusion, then i will inform the cdrkit project
about it.

We have an individual drive here which behaves different than normal.
If my current theory is right and if your man page is still correct
about the default of 40 seconds, then cdrecord might be affected too.

But first we have to see a successful run with RESERVE TRACK.
It is unlikely that the successful cdrskin run used that command.
I am not sure about the successful growisofs run.
So the proposed experiment is essential for deciding this question:
Is the sparse timeout to blame or is it the command generally ?


As for timeouts: They should not happen on the first hand. I see
few use in not waiting several minutes before aborting the SCSI
transaction. Afterwards there is a high probability that the run
is spoiled anyway.


Have a nice day :)

Thomas