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.
2.2.13.4 Procedure for de-allocating metadata blocks.<br />
Set (to one) the bit(s) in the Metadata Bitmap file corresponding to the block number(s)<br />
of the data within the Metadata Partition that is being de-allocated.<br />
2.2.13.5 Recommended procedure for extending the Metadata Partition<br />
These changes should be written to the device before the new blocks are allocated for use<br />
by metadata. It would be undesirable for such changes to sit in an implementation’s write<br />
cache for so long that new metadata assigned to the blocks being described by the<br />
changes was written to the media first.<br />
1. Verify that t<strong>here</strong> is enough space in the Metadata File and Metadata Mirror File<br />
Allocation Descriptor chains for a new Allocation Descriptor. If not then allocate<br />
a new Allocation Descriptor extent.<br />
2. Verify that the Metadata Bitmap file allocation is large enough to extend the<br />
bitmap to describe the additional blocks added to the Metadata File, and if not<br />
then allocate block(s) for the Metadata Bitmap file.<br />
3. Allocate a new extent of blocks (for the Metadata File) observing the size and<br />
alignment requirements specified in2.2.13.1.<br />
4. If the Duplicate Metadata Flag in the Metadata Partition Map Flags field is set,<br />
allocate a second extent of blocks observing the size and alignment requirements<br />
specified in2.2.13.1, ideally as far away as possible from the first allocation (for<br />
the Metadata Mirror File).<br />
5. Add a new Allocation Descriptor to the Metadata File, or modify existing<br />
descriptors, to reference the first newly allocated extent. If the Duplicate<br />
Metadata Flag in the Metadata Partition Map Flags field is not set, modify the<br />
Metadata Mirror file ADs to reference the same extent.<br />
6. If a second extent of blocks was allocated above, add to the Metadata Mirror File<br />
a new Allocation Descriptor, or modify existing ADs, to reference this second<br />
extent.<br />
7. If the new extents were added at the end of the Metadata File then increase the FE<br />
Information Length for the Metadata File, and Mirror, to include the new blocks.<br />
8. If the Metadata Bitmap file was extended, increase its FE Information Length<br />
field to include the bits describing the additional blocks allocated to the Metadata<br />
files.<br />
9. Set (set to one) the bits in the Metadata Bitmap file which correspond to the extent<br />
just added to the Metadata file, to indicate the blocks are available for use by new<br />
metadata.<br />
UDF 2.01<br />
45<br />
March50 April