Re: BD-R formatting help
> But doesn't the POW gesture make session 1
> unmountable as soon as a further session
> is recorded ?
??? Why should it? It's just that last- and first-session mounts will be
equivalent.
> Even on a drive which would recognize and
> handle multi-session ?
First session effectively grows and it has nothing to do with drive
recognizing multi-session. As you hinted yourself, -o sbsector=16 works
even when drive handles multi-session.
> Accessing older sessions is helpful with
> incremental backups.
Then you want to format for SRM-POW (SRM minus POW, i.e. *without* POW),
in which case it will behave exactly as multi-session write-once. As
mentioned on the page SRM+POW is chosen as default to maintain broadest
accessibility by making all the data available even in non-multi-session
aware OSes.
> With overwriteables i write the first session
> to LBA 32 and do the patching of LBA 0 to 31
> already with that first session. An interested
> reader can mount -o sbsector=32 and thus access
> session 1 even if LBA 0 to 31 gets overwritten
> later.
Cool.
> All other sessions can easily be found by our NWA
> rounding (you 16, me 32). They form a nice chain.
>
> I could imagine that this would work with BD-R
> POW too.
Yes it would. Except that other sessions would have to be identified by
looking at track start addresses instead of volume size round ups.
> Hopping over the orphans will make scanning for
> sessions more cumbersome. This would apply to
> drives which would need your POW patching.
Drives don't need it! Some OSes would. Or I misunderstood the question,
in which case please rephrase. A.
Reply to: