Re: BD-R formatting help
SRM+POW recordings are *not*. SRM+POW recordings are
multi-track, but not multi-session. Meaning that even multi-session aware OS
will look for volume descriptor at LBA#16 for SRM+POW recording.
[...]
I leave session open in SRM+POW
[...]
appropriate to refer to recording as "increment", not "session", in SRM+POW
So it is very similar to our layouts on
overwriteable media. Except that the NWA
is prescribed by the new track and not
at the discretion of the burn program.
(MMC advises to use the track provided NWA
in 4.5.3.6.9 "The Expanding Orphanage".)
Yes.
I have to split the meaning of "Session"
for clarity.
There are no MMC-sessions on overwriteables
and on BD-R+POW (as written by growisofs).
But there are ISO-sessions or Volumes which
get generated as if they were to be appended
to MMC-multi-session media. (This stems from
ISO 9660 on CD-R, after all.)
Right.
I plead for keeping the ISO-sessions
distinguishable in order to allow to mount
the older states of the (pseudo-)multi-session
media. ...........
I'll definitely consider all the suggestions.
---------------------------------------------------
For reference, according to READ TRACK INFORMATION
end of any given track coincides with start of next
one.
Now this is a riddle. From where did POW take the
clusters which replaced the old LBA 0 clusters ?
Presumably from past the end of user data.
The specs say
"the Logical Overwrite of a Cluster
is redirected to the NWA of some open Logical Track."
"A SRM disc with POW shall be initialized by
the formatting process as a single session disc with
a single Logical Track."
The latter statement seems to forbid your track
structure. Duh ?
No. It only says how it should be *initially* formatted, but says
nothing about that it shall stay that way for eternity.
Anyway. If there is only one open track then the
cluster had to be taken from its NWA.
After transfer of iso-formatted volume NWA is at its end, right? When
LBA 0 is overwritten, space is borrowed from NWA, which increments[!]
NWA. *Then* current track is closed. So next track's NWA starts at
cluster past borrowed space and no avalanche takes place. But [as
mentioned earlier] end of track does not necessarily coincides with end
of recording, iso-formatted volume in this case.
If you start the next track and inquire its NWA
then i'd expect it skips the orphaned cluster address.
It does.
If it would use the orphan LBA for the start of a
sequential write, then an avalanche of orphans would
hit the Defect List.
POW-aware recording program is expected to check on NWA after every
write and handle its changes accordingly. In growisofs case single check
in the beginning of recording suffices. A.
Reply to: