K3b: Cannot continue a multisession project

English Applications
#1

Hi!
I’m using K3b 2.10.0.
I just burn a CD-RW medium with “Multisession Mode: Start Multisession” property, with some data.
And when I want to “Continue Multisession Project”, the “Session Import” dialog appears with the right session in it. But that session is not imported, so I cannot continue it.
(The same CD was used on the same CD/DVD device to do the same operation in openSuse 13.2, and that did work fine.)

Can somebody help me?

Thank you in advance.

#2

How large is your existing image?
From what I understand (from long ago) the previous session is imported to create a new session which includes the old and the old data becomes dead space.

If you don’t have enough room to import the old session <and> add new data, then you… just can’t.

If you don’t know your current disk’s usage, writers like k3b should have an “analyze” tool to read the current disk.

TSU

#3

The size of the files in CD is 17M as you can see in /dev/sr0:

adrian@asia:~> df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           2.0G   57M  1.9G   3% /dev/shm
tmpfs           2.0G  2.5M  2.0G   1% /run
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/sdb3        94G   15G   78G  16% /
/dev/sdb3        94G   15G   78G  16% /var/log
/dev/sdb3        94G   15G   78G  16% /.snapshots
/dev/sdb3        94G   15G   78G  16% /var/cache
/dev/sdb3        94G   15G   78G  16% /var/lib/mariadb
/dev/sdb3        94G   15G   78G  16% /usr/local
/dev/sdb3        94G   15G   78G  16% /var/lib/mysql
/dev/sdb3        94G   15G   78G  16% /var/lib/named
/dev/sdb3        94G   15G   78G  16% /var/lib/machines
/dev/sdb3        94G   15G   78G  16% /var/opt
/dev/sdb3        94G   15G   78G  16% /var/tmp
/dev/sdb3        94G   15G   78G  16% /var/spool
/dev/sdb3        94G   15G   78G  16% /var/crash
/dev/sdb3        94G   15G   78G  16% /var/lib/mailman
/dev/sdb3        94G   15G   78G  16% /var/lib/libvirt/images
/dev/sdb3        94G   15G   78G  16% /var/lib/pgsql
/dev/sdb3        94G   15G   78G  16% /tmp
/dev/sdb3        94G   15G   78G  16% /srv
/dev/sdb3        94G   15G   78G  16% /opt
/dev/sdb4       831G  8.8G  821G   2% /home
/dev/sda5       250G  108G  143G  43% /DATA
/dev/sdb1       255M   70M  167M  30% /boot
tmpfs           396M     0  396M   0% /run/user/481
tmpfs           396M   12K  396M   1% /run/user/1000
/dev/sr0         17M   17M     0 100% /run/media/adrian/Imp&Serv
adrian@asia:~>

Thank you .

#4

It’s probably more important to know how k3b thinks your data disk is used, not what you’ve mounted.

As I described in my previous post, every disk burning app has an “Analyze” tool that reads what is already on the disk, and might verbosely describe what is possible… eg. data utilization, whether the disk is still considered multi-session or might have been closed.

TSU