>From [EMAIL PROTECTED] Tue Nov 19 18:30:19 2002

>> >Apparently the delay between
>> >"write" commands breaks -dao mode. The problem seem to be that cdrecord
>> >incorrectly estimates one of the first delays which results in buffer
>> >underrun condition and "toasted" media. As we know first write commands
>> >"take" longer time in SAO mode as the unit has to first burn lead-in,
>> >which must be the explanation.
>> 
>> It does not incorrectly estimate the time... There is an upper limit that
>> prevents buffer underrun.
>> 
>> If you have problems, send useful information.

>cdrecord dev=x,y,z -immed -v -dao -useinfo *.wav
>...
>Track 01:    1 of   32 MB written (fifo 100%) [buf  98%] |307  836ms|   0.4x
>CDB:  2A 00 00 00 01 EC 00 00 1B 00
>status: 0x2 (CHECK CONDITION)
>Sense Bytes: 71 00 05 00 00 00 00 0C 00 00 00 00 10 02 00 00
>Sense Key: 0x5 Illegal Request, deferred error, Segment 0
>Sense Code: 0x10 Qual 0x02 (id crc or ecc error) [No matching qualifier] Fru 0x0
>Sense flags: Blk 0 (not valid) 
>cmd finished after 3.424s timeout 200s

>The failing LBA seem varies with burning speed. 0x1EC was observed at 10x,
>while 12x burn failed at LBA 0x3B7. The unit has 2MB buffer.

Mmmm what drive?


There two probable reasons:

-       that the drive lies about it's buffer :-(

-       The OS does a very incorrect usleep(3)

307 2352 * p
722064

If the drive reports 2 MB and 98% full, then it holds ~ 2000 kb.
Waiting 836 ms is ~ 627 sectors at 10x == 1474704 bytes

To have more reserve  for improbability, try to change

        mt = per*(bsize/secsize)/100 * 1000 / secsps/s;
to
        mt = (per-50)*(bsize/secsize)/100 * 1000 / secsps/s;

J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to