- Universal Disk Format
The Universal Disk Format (UDF) is a format specification of a
file systemfor storing files on optical media. It is an implementation of the ISO/IEC 13346 standard (also known as ECMA-167). It is considered to be a replacement of ISO 9660, and today is widely used for (re)writable optical media. UDF is developed and maintained by the Optical Storage Technology Association(OSTA).
The UDF file system was standardized by the
Optical Storage Technology Associationto form a common file system for all optical media. The goal was to make a common file system for read-onlymedia, and optical media that are re-writable. This is still the main goal for ongoing UDF standardization, although support for the more obscure WORM media is about to be limited, and support for non-optical media may be added.
When it was first standardized, the UDF file system was intended to replace ISO 9660, allowing support for both read-only and writable media. Almost directly after the first version of UDF was released, it was adopted by the
DVD Consortiumas the official file system for DVD Videoand DVD Audio. Nowadays, a UDF file system may be found on most authored optical discs in the market, and on almost all recordable DVDmedia that are used for video recording.
As intended, initially UDF was mainly found on optical media. Most operating systems needed special third-party software to support reading it. Nowadays, almost all operating systems natively support at least reading UDF file systems, and many support some form of writing as well. Because of this increased support, UDF is gaining popularity on non-optical media that mainly need to be exchangeable, such as
Iomega REVdiscs, large flash media, and even on hard disk drives.
DVD-Videomedia use UDF version 1.02. These discs contain a so-called UDF Bridge format, whereby both an ISO 9660 (Level 1) and a UDF 1.02 filesystem are present on the same disc, describing the same filesystem.
All standard formats for video recording on
DVD-style media use some version of the UDF filesystem.
DVD+VRformat uses UDF 1.02 with an ISO 9660 bridge for DVD+Rand DVD+RW.
DVD Forum's DVD-VRformat uses UDF 2.00 for DVD-R, DVD-RWand DVD-RAM.
Blu-raywill be using UDF 2.50 or UDF 2.60.
Hyper Scangame console uses a version of UDF for the game data
A UDF file system is normally mastered by authoring software in a batch process, and written to disc in a single pass. But when
packet writingto rewriteable media, such as CD-RW, UDF allows files to be created, deleted and changed on-disc just as a general-purpose filesystemwould on removable media like floppy disks and flash drives. This is also possible on write-once media, such as CD-R, but in that case the space occupied by the deleted files cannot be reclaimed (and instead becomes inaccessible).
The specification allows for nine character encodings: One by agreement, one specified by
ECMA-6 (also known as ASCII), three subsets of ASCII, a subset of ECMA-94 ( Latin-1), and various other graphical characters.
Revisions of UDF
UDF has been released in multiple revisions:
* Revision 1.02 (August 30, 1996). This format is used by
* Revision 1.50 (February 4, 1997). Added support for (virtual) rewritability on CD-R/DVD-R media by introducing the VAT structure. Added sparing tables for defect management on rewritable media such as CD-RW, and DVD-RW and DVD+RW.
* Revision 2.00 (April 3rd, 1998). Added support for Stream Files and real-time files (for DVD recording) and simplified directory management. VAT support was extended.
* Revision 2.01 (March 15, 2000) is mainly a bugfix release to UDF 2.00. Many of the UDF standard's ambiguities were resolved in version 2.01.
* Revision 2.50 (April 30, 2003). Added the Metadata Partition facilitating metadata clustering, easier crash recovery and optional duplication of file system information: All metadata like nodes and directory contents are written on a separate partition which can optionally be mirrored.
* Revision 2.60 (March 1, 2005). Added Pseudo OverWrite method for drives supporting pseudo overwrite capability on sequentially recordable media.
For next releases of UDF, changes are discussed in relation to using UDF on very large hard disk media, and using UDF on
Builds of UDF
While the UDF specification has never been explicit about it, all UDF revisions since 1.5 actually describe three different variations of the format.
These builds are:
* Plain (Random Read/Write Access). This is the original format supported in all UDF revisions
* VAT (Incremental Writing). Used specifically for writing to CD-R and (write-once) media
* Spared (Limited Random Write Access). Used specifically for writing to CD-RW and DVD-RW (rewritable) media
This format can be used on any type of disk that allows random read/write access, such as hard disks, DVD+RW and DVD-RAM media. Similar to other common file system formats, such as FAT, directory entries point directly to the block numbers of their file contents. When writing to such a disk in this format, any physical block on the disk may be chosen for allocation of new or updated files.
Since this is the "basic" format, practically any OS or File System Driver claiming support for UDF should be able to read this format.
DVD-R and CD-R media have limitations when being written to, in that each physical block can only be written to once, and the writing must happen incrementally. Thus the "plain" build of UDF can only be written to CD-Rs by pre-mastering the data and then writing all data in one piece to the media, similar to the way ISO 9660 gets written to CD media.
To enable CD-R to be used virtually like a hard disk, whereby the user can add and modify files on a CD-R at will (so-called "drive letter access" on Windows), OSTA added the "VAT" build to the UDF standard.
The VAT is an additional structure on the disk that helps remapping physical blocks when files or other data on the disc are modified. The write-once nature of the media means that when a file is first added and then deleted on the disk, the file's data still remains on the disk. It does not appear in the directory any more, but special tools can be used to access the previous state of the disc (the state before the delete occurred), making recovery possible. Eventually the disk will be full, as free space cannot be recovered by deleting files. However, this behavior can be used to advantage for the purpose of archiving data.
Understanding the VAT structure is necessary in order to read such discs, but not all UDF file systems support VAT. See also "Why your computer might not read a particular UDF disk", below.
Spared (RW) build
DVD-RW and CD-RW media have fewer limitations than DVD-R and CD-R media. Sectors can be rewritten at random (though in packets at a time). These media can be erased entirely at any time, making the disc blank again, ready for writing a new UDF or other file system (e.g. ISO 9660 or CD Audio) to it.
DVD-RW and CD-RW disks may thus be used as a blankable-R media but may also be formatted in the "plain", "VAT" and "Spared" UDF builds.
However, it is important to understand that sectors of "-RW" media may "wear out" after a while, meaning that their data becomes unreliable, through having been rewritten too often (typically after a few hundred rewrites, with CD-RW).
If the "plain" build is used on a-RW media, file-system level modification of the data must not be allowed, as this would quickly wear out often-used sectors on the disc (such as for directory and block allocation data), which would then go unnoticed and lead to data loss. Hence, if software formats -RW media with UDF in the "plain" build, it should set the "hard write protection" flag on the volume to ensure that no UDF software attempts to overwrite files on the volume like it's possible with random-rewritable media such as hard disks.
To allow modification of files on the disc, the media can be used like -R media using the "VAT" build. This ensures that all blocks get written only once (successively), ensuring that there are no blocks that get rewritten more often than others. This way, a RW disc can be erased and reused many times before it should become unreliable.
To get true overwritability (which is not possible with the "VAT" build) of files on RW media, the disc needs to be formatted using the "Spared" build which adds an extra "Sparing Table". This table keeps track of bad sectors and remaps them to working ones.
Once a -RW disc has been used with the "spared" UDF build, the disc should never get re-used with any other format, as the information about the bad blocks would get lost, potentially leading to the aforementioned unreliability.
Since DVD+RW discs can't emulate DVD+R, they can only be formatted in the "plain" and in the "Spared" UDF build.
Consequences of using specific builds
The consequences of using these builds are as follows:
* When using the "plain" build, in theory a disc driver may allow rewriting any disc sector at random, meaning the RW is truly rewritable in the fashion of hard disks. However, because of the wear-out effect, this would soon lead to loss of data. For that reason, if a "plain" UDF file system is written to RW media, the file system should lock (write protect) the UDF volume to prevent accidental modification by a computer, or better, disc drivers should never even attempt to provide random-write access to RW media unless they can assure that no data loss due to wear-out can happen.
* When using the "VAT" build, CD-RW/DVD-RW media effectively appears as CD-R or DVD+/-R media to the computer. However, the media may be erased again at any time.
* Finally, the "Spared" build works basically like the "plain" build, but uses an extra "Sparing Table" to remap worn-out sectors.
Understanding Sparing Tables is necessary to be able to read discs written in "Sparable" build correctly. The problem is that some existing versions of UDF File System software ignore this extra information and treat such UDF discs as if they had the "plain" build. As long as the media has no worn-out sectors, this does not matter - the files can be read properly. But once sectors are remapped, a File System not paying attention to the Sparing Table will read outdated sectors, leading to retrieval of the wrong data.
Why a computer might not read a particular UDF disk
Even if a computer claims to be able to read UDF 1.50, it still may only support the "plain" build and not necessarily either the "VAT" or "Spared" build.
An example is Mac OS X (10.4.5), which claims to support UDF 1.50 (see "man mount_udf"), yet it can only mount disks of the "plain" build properly (it cannot mount UDF disks with a VAT at all, [http://docs.info.apple.com/article.html?artnum=75503 see Sony Mavica problem] , and while it appears to be able to mount CD-RWs written with a Sparing Table, it does not read its files correctly in the case that files are actually remapped).
Standalone DVD player compatibility
Some users have reported that video DVDs burned on their computers in UDF version 1.5 are not compatible with their set-top video DVD players. These players seem to be only compatible with UDF version 1.02 (that provides both UDF and ISO 9660 directories.) As some popular DVD burning programs default to UDF version 1.5 when burning video DVDs, users have found it necessary to avoid using the software wizard and instead manually configure the burn to version 1.02.
Philips provides source code and binaries for a UDF verifier that examines media for UDF compliance.cite web | url=http://www.ip.philips.com/services/?module=IpsVisitorLogin | title=UDF Verification Software | date=
2007-11-25| accessdate=2007-11-25 | publisher=Philips]
* ISO/IEC 13346 standard, also known as [http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-167.pdf ECMA-167] .
Native OS support
Terminology::* Unless otherwise noted, "read" and "write" support means that only the "plain" UDF build is supported, but not the "VAT" and "spared" build.:* Support for "read" means that a UDF formatted disk can be mounted by the system. It enables the user to read files from the UDF volume using the same interface that is used to access files on other disks connected to the computer.:* Support for write means that, additionally to reading files from a mounted UDF volume, data such as files can also be modified, added, or deleted.
* [http://www.osta.org/ OSTA home page]
* [http://homepage.mac.com/wenguangwang/myhome/udf.html Wenguang Wang's UDF Introduction]
* [http://sourceforge.net/projects/linux-udf/ Linux UDF support]
* [http://support.microsoft.com/kb/321640/en-us Microsoft Windows UDF Read Troubleshooting]
* [http://www.burnworld.com/dvd/primer/filesystem.htm UDF Primer]
* [http://www.osta.org/specs/pdf/udf260.pdf UDF Revision 2.60] March 1, 2005
Wikimedia Foundation. 2010.