Re: Burning and mounting written BDs

[Thomas Schmitt]

Hi,

Kjetil Kjernsmo wrote:
> OK, I had a single 25 GB M-disc left, so I just started writing to that,
> fingers crossed!

I meanwhile made up a theory about the failure to mount which you report
in the first mail of this thread:
If you did not eject and reload the medium between burning and mount
attempt, then you fell victim to a known problem with burning on Linux.
The change of medium state and readable size does not get known to the
kernel automatically and there are no means to tell the kernel to
re-assess the medium. The only way to force re-assessment is to eject and
reload.

growisofs under K3D probably did an eject-and-reload cycle.
With xorriso you may eject by appending the following commands to the
xorriso burn run:

  -commit -eject all -outdev /dev/sr0

This will burn, eject, load again, and wait until the drive reports to
be ready. (Linux does not wait properly any more since march 2008.)

xorriso's own drive state assessment does not depend on the kernel's
idea of the medium state. So it has no problem with checkreading
directly after burning.


> Alright, OK! I have previously used this [drive] successfully even with
> 100 GB M-Disc

But did you checkread all data content afterwards ?
If my above theory is correct, then the readability problem with higher
block addresses might not be new.


Have a nice day :)

Thomas