here - OSTA - Optical Storage Technology Association
here - OSTA - Optical Storage Technology Association
here - OSTA - Optical Storage Technology Association
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
non-overlapping Partitions with 2 prevailing Partition<br />
Descriptors only if one has an access type of read<br />
onlyRead-Only and the other has an access type of<br />
Rewritable, Overwritable, or WORM. Write-Once. The<br />
Logical Volume for this volume would consist of the<br />
contents of both partitions.<br />
Logical Volume Descriptor<br />
T<strong>here</strong> shall be exactly one prevailing Logical Volume<br />
Descriptor recorded per Volume Set.<br />
The LogicalVolumeIdentifier field shall not be null and<br />
should contain an identifier that aids in the identification of<br />
the logical volume. Specifically, software generating<br />
volumes conforming to this specification shall not set this<br />
field to a fixed or trivial value. Duplicate disks, which are<br />
intended to be identical, may contain the same value in this<br />
field. This field is extremely important in logical volume<br />
identification when multiple media are present within a<br />
jukebox. This name is typically what is displayed to the<br />
user.<br />
Logical Volume Integrity Descriptor<br />
Unallocated Space Descriptor<br />
File Set Descriptor<br />
ICB Tag<br />
File Identifier Descriptor<br />
File Entry<br />
Allocation Descriptors<br />
Allocation Extent Descriptors<br />
Unallocated Space Entry<br />
Space Bitmap Descriptor<br />
Partition Integrity Entry<br />
Volume Descriptor Sequence Extent<br />
The LogicalVolumeDescriptor recorded on the volume<br />
w<strong>here</strong> the PrimaryVolumeDescriptor’s<br />
VolumeSequenceNumber field is equal to 1 (one) must have<br />
a NumberofPartitionMaps value and PartitionMaps<br />
structure(s) that represent the entire logical volume. For<br />
example, if a volume set is extended by adding partitions,<br />
then the updated LogicalVolumeDescriptor written to the<br />
last volume in the set must also be written (or rewritten) to<br />
the first volume of the set.<br />
Shall be recorded. The extent of LVIDs may be terminated<br />
by the extent length.<br />
A single prevailing Unallocated Space Descriptor shall be<br />
recorded per volume.<br />
T<strong>here</strong> shall be exactly one File Set Descriptor recorded per<br />
Logical Volume on Rewritable/Overwritable media. For<br />
WORM media multiple File Set Descriptors may be<br />
recorded based upon certain restrictions defined in this<br />
document. The FSD extent may be terminated by the extent<br />
length.<br />
Only strategy types 4 or 4096 shall be recorded.<br />
The total length of a File Identifier Descriptor shall not<br />
exceed the size of one Logical Block.<br />
The total length of a File Entry shall not exceed the size of<br />
one Logical Block.<br />
Only Short and Long Allocation Descriptors shall be<br />
recorded.<br />
The length of any single extent of allocation descriptors<br />
shall not exceed the Logical Block Size.<br />
The total length of an Unallocated Space Entry shall not<br />
exceed the size of one Logical Block.<br />
CRC not required.<br />
Shall not be recorded.<br />
Both the main and reserve volume descriptor sequence<br />
UDF 2.01<br />
9<br />
March50 April