[k3b] [Bug 379268] Importing previous session does nothing (version 17.04.0)

[Thomas Schmitt]

https://bugs.kde.org/show_bug.cgi?id=379268

--- Comment #21 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,

> I always choose pure UDF from the list of options.

Now that's a starting point for Leslie's investigations.
Does K3B, when importing a session, take into respect that it is UDF
and does this have consequences for its further preparations of the
mkisofs run ?

My local genisoimage program happily appends an UDF session to an UDF
filesystem on an appendable sequential DVD-RW. But afterwards the added
files are not visible when the medium gets mounted.
Obviously my Linux 3.16 mounts session 1. If i force it to load the
newly added session:

  mount -o sbsector=119344 /dev/sr3 /mnt/iso

i get

  mount: wrong fs type, bad option, bad superblock on /dev/sr3,

Nevertheless if xorriso loads the second session via the ISO 9660 tree,
then it sees all files from both sessions. The same positive result can
be seen if i force Linux to use ISO 9660:

  mount -t iso9660 -o sbsector=119344 /dev/sr3 /mnt/iso

So we can conclude that at least older mkisofs spoils UDF on multi-session.

Possibly K3B is aware of this and refrains without a clear error message.


> >   https://bugs.kde.org/show_bug.cgi?id=367639#c44

> I had this problem on DVDs too.

I guess this was a different one. The symptom of 367639 was this error
message:
  /usr/bin/growisofs: -C argument is insane.
which we after some forth and back identified as caused by a deviation
between K3B and growisofs when it came to the prediction of the Next
Writable Address of the medium.


> After burning new files, all files from
> previous session had size of 0 B. One could see that in Dolphin.

Looks like a another bug. Number three in our local counting.

The file size in the result is hardly influencable by K3B. This is in
the responsibility of the ISO 9660 or UDF producer program. Normally
mkisofs or genisoimage.


Have a nice day :)

Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.