All approved UDF 2.60 DCNs

All approved UDF 2.60 DCNs
DCN-5104
Document: OSTA Universal Disk Format
Subject: Next extent for Metadata File and Metadata Mirror File
Date: September 16, 2003; modified September 14, 2004.
Description:
Outcome of UDF Committee meeting September 15, 2003 and September 14, 2004:
The requirements for the Allocation Descriptors in File Entry of Metadata File and
Metadata Mirror File are amended, see 2.2.13.1.
• For 2nd bullet, type “next extent of allocation descriptors” is also allowed.
• For 3rd bullet, the extent length is described in bytes instead of logical blocks and
the rule is not valid for extent type “next extent of allocation descriptors”.
• For 4 th bullet, the rule only makes sense for extent type “recorded and allocated”.
This DCN is meant for the next UDF revision after 2.50 and for the UDF 2.50 errata.
Change:
In 2.2.13.1 Metadata File (and Metadata Mirror File)
replace last 3 bullets of first bullet list:
by:
• …
• Either be of type “allocated and recorded” or type “not allocated”.
• Have an extent length that is an integer multiple of the Allocation Unit Size
specified in the Metadata Partition Map.
• Have a starting logical block number which is an integer multiple of the
Alignment Unit Size specified in the Metadata Partition Map.
• …
• Not specify an extent of type “not recorded but allocated”.
• Extents of type “recorded and allocated” or “not allocated” shall have an extent
length that is an integer multiple of (Allocation Unit Size multiplied by logical
block size). The Allocation Unit Size is specified in the Metadata Partition Map.
• Extents of type “recorded and allocated” shall have a starting logical block
number that is an integer multiple of the Alignment Unit Size specified in the
Metadata Partition Map.
All approved UDF 2.60 DCNs 21 February 28, 2005