Note that as of May 2003 I've decided to advise users to turn to <[EMAIL PROTECTED]> on support matters. Subscribe page is at http://lists.debian.org/cdwrite/, archive - at http://www.mail-archive.com/cdwrite%40other.debian.org/.
OK. I subbed and cc'ed the list. If you wish to continue this in either way, that's fine with me.
When I invoked growisofs as follows: growisofs -Z /dev/cdrom -R -J -dvd-compat and the overburn protection kicked in, it still wrote data to the DVD+R.
I can't repoduce this. Define "kicked in." Take for habit to include exact output from growisofs, not how you interpret it. What version is it? Verify with growisofs -version. Complement report with output from dvd+rw-mediainfo.
Gah. I should know better. growisofs version is 5.5, front-ending to mkisofs 2.0 (i686-pc-linux-gnu). I don't have dvd+rw-mediainfo on my box. cdrecord -scanbus reports:
scsibus1:
1,0,0 100) 'MITSUMI ' 'DW-7801TE ' '1.01' Removable CD-ROMIt's an IDE drive using ide-scsi emulation. I'm using Sony DVD+R discs, and they seem to work flawlessly with smaller amounts of data.
Here's what happens when I run it on the 4.3 GB file, which you claim that the media should be able to use, below.
[EMAIL PROTECTED] root]# ls -sh /mnt/backups/toburn/
total 9.0G
4.5G home.001 4.3G home.002 286M var.001
[EMAIL PROTECTED] root]# growisofs -Z /dev/cdrom -R -J -dvd-compat /mnt/backups/toburn/home.002
Executing 'mkisofs -R -J /mnt/backups/toburn/home.002 | builtin_dd of=/dev/cdrom obs=32k seek=0'
mkisofs: Value too large for defined data type. File /mnt/backups/toburn/home.002 is too large - ignoring
Total translation table size: 0
Total rockridge attributes bytes: 169
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 5024
48 extents written (0 Mb)
/dev/cdrom: flushing cache
/dev/cdrom: closing track
/dev/cdrom: closing disk
/dev/cdrom: reloading tray
I expect that the data was written because of the -dvd-compat option.
Can't reproduce it with or without -dvd-compat...
I honestly didn't check without -dvd-compat. I've blown too many discs.
It would be good for growisofs to recognize that and avoid writing any data if an overburn would happen.
I'm writing very large dump files to a DVD, and even a file that Linux reports as being 4.3 GB seems to be too big.
DVD can accomodate 4.3GB. It might be bad media. Another user for example reported and all attempts to record media of certain brand were terminated at ~95% of advertised capacity. What's your unit and what's your media? A.
Chad Martin
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
