Error writing blu ray data discs with k3b?

elfoozo · 12-05-2010, 12:56 PM

Does k3b require free hard drive space at the finalize media stage?

I'm trying to write a 17.6 GB file to 25 GB media with 18 GB free space on the hard drive.

My disc seems to write 100% then displays "Error". This is the debugging code:

Code:

Burned media
-----------------------
BD-R Sequential (SRM)

Devices
-----------------------
HL-DT-ST BD-RE  WH10LS30 1.00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 9227262 (18897432576 bytes)

System
-----------------------
K3b Version: 2.0.1
KDE Version: 4.4.5 (KDE 4.4.5)
QT Version:  4.6.3
Kernel:      2.6.32-5-amd64

Used versions
-----------------------
mkisofs: 1.1.11
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: pre-formatting blank BD-R for 24.8GB...
/dev/sr0: "Current Write Speed" is 8.2x4390KBps.
   19136512/18897432576 ( 0.1%) @1.3x, remaining 49:19 RBU 100.0% UBU  50.0%
[snip]
18849333248/18897432576 (99.7%) @3.4x, remaining 0:03 RBU 100.0% UBU  50.0%

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:9227262 -speed=8 -use-the-force-luke=bufsize:32m

mkisofs
-----------------------
9227262
I: -input-charset not specified, using utf-8 (detected in locale settings)
This size can only be represented in the UDF filesystem.
Make sure that your clients support and use it.
ISO9660, Joliet, RockRidge, HFS will display incorrect size.
  0.01% done, estimate finish Sun Dec  5 11:58:27 2010
=== last message repeated 2 times. ===
  0.02% done, estimate finish Sun Dec  5 11:58:27 2010
[snip]
 99.99% done, estimate finish Sun Dec  5 12:22:49 2010
100.00% done, estimate finish Sun Dec  5 12:22:49 2010
Total translation table size: 0
Total rockridge attributes bytes: 282
Total directory bytes: 416
Path table size(bytes): 10
Max brk space used 0
9227262 extents written (18021 MB)

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid MYDATA -volset  -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-me/k3bEZ1534.tmp -rational-rock -hide-list /tmp/kde-me/k3bcp1534.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-me/k3bvs1534.tmp -no-cache-inodes -allow-limited-size -udf -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-me/k3bFd1534.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid MYDATA -volset  -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-me/k3bAd1534.tmp -rational-rock -hide-list /tmp/kde-me/k3bbb1534.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-me/k3bDI1534.tmp -no-cache-inodes -allow-limited-size -udf -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-me/k3bWn1534.tmp

garydale · 12-06-2010, 10:17 AM

It seems like you are tight on disk space for a large project like that. Have you considered simply adding another disk drive? They're cheap enough these days to get you enough space to handle anything you throw at it.

Even an external USB drive (esp. if you are using a notebook) seems like a reasonable option to ensure that disk space is not a concern.

elfoozo · 12-06-2010, 07:38 PM

I added a 2 TB SATA drive, formatted, mounted and changed the settings in k3b to point $tmp to the new drive.

Error still happens.

garydale · 12-06-2010, 11:29 PM

I'd move your entire project over. Or possibly even migrate /home to your new drive. Having just enough free space on your main drive isn't all that good. You could even try partitioning the new drive into two or three partitions. Make one /home, another /tmp and maybe a third as /var.

Having 2T free isn't good enough if it's not where k3b needs the space.

elfoozo · 12-09-2010, 08:06 AM

The only lead I could find while googling was to set multi-sessions to no multi-session in my projects which I've done but get the same error. I also switched my project data files, partitions and temp files over to the gigantic free space but still get the same type of error. I'm reasonably comfortable that it's not the project because I'm picking different "source" data files on each burn and also creating new projects each time. The genisoimage lines have

Code:

/mnt/sdb1/tmp/kde-me/k3bEZ1534.tmp

as an example of their path.

It certainly seems like k3b has the space where it needs it. And what's interesting is I can eject/reinsert the media then mount it and the files look and display correctly.

Thoughts?