1UDFINFO(1) General Commands Manual UDFINFO(1)
2
6 udfinfo — show information about UDF filesystem
7
10 udfinfo [ options ] device
11
14 udfinfo shows various information about a UDF filesystem stored either
15 on the block device or in the disk file image. The output from the
16 udfinfo is suitable for parsing by external applications or scripts.
17
20 -h,--help
21 Display the usage and the list of options.
22 -b,--blocksize= block-size
25 Specify the size of blocks in bytes. Valid block size for a UDF
26 filesystem is a power of two in the range from 512 to 32768 and
27 must match a device logical (sector) size. If omitted, udfinfo
28 tries to autodetect block size. First it tries logical (sector)
29 size and then all valid block sizes.
30 --vatblock= vat-block
33 Specify the block location of the Virtual Allocation Table. Vir‐
34 tual Allocation Table is present only on UDF disks with Virtual
35 Partition Map and must be at the last written/recorded disk
36 block.
37 If omitted, udfinfo for optical disc tries to detect the last
39 recorded block with fallback to the last block of block device
40 or disk file image. In most cases, this fallback does not have
41 to work and for disk file images with Virtual Allocation Table
42 is necessary to specify the correct location.
43 Virtual Allocation Table contains locations of UDF disk blocks
45 needed to read data storage, determinate used and free space
46 blocks, read File Set Identifier and calculate Windows-specific
47 Volume Serial Number. Also, it contains Logical Volume Identi‐
48 fier and overwrite previously stored in Logical Volume Descrip‐
49 tor.
50 --locale
53 Encode UDF string identifiers on output according to current
54 locale settings (default).
55 --u8 Encode UDF string identifiers on output to 8-bit OSTA Compressed
58 Unicode format without leading Compression ID byte, which is
59 equivalent to Latin1 (ISO-8859-1). This will work only for
60 strings which Unicode code points are below U+100.
61 --u16 Encode UDF string identifiers on output to 16-bit OSTA Com‐
64 pressed Unicode format without leading Compression ID byte,
65 which is equivalent to UTF-16BE.
66 --utf8 Encode UDF string identifiers on output to UTF-8.
69
72 udfinfo returns 0 if successful, non-zero if there are problems like a
73 block device does not contain UDF filesystem.
74
77 First part of the udfinfo standard output contains information in
78 key=value format. List of all keys with their meaning are in the fol‐
79 lowing table:
80 filename File name of the selected block device or disk
83 file image
84 label label is an alias for lvid, see udflabel(8)
86 section UDF LABEL AND UUID
87 uuid UUID are first 16 hexadecimal lowercase digits
89 of fullvsid, but see udflabel(8) section UDF
90 LABEL AND UUID
91 lvid UDF Logical Volume Identifier stored in UDF
93 Logical Volume Descriptor
94 vid UDF Volume Identifier stored in UDF Primary
96 Volume Descriptor
97 vsid fullvsid after uuid part, typically 17.–127.
99 character
100 fsid UDF File Set Identifier stored in UDF File Set
102 Descriptor
103 fullvsid UDF Volume Set Identifier stored in UDF Primary
105 Volume Descriptor
106 winserialnum Windows-specific Volume Serial Number
108 blocksize UDF block size
110 blocks Number of all blocks on the selected block
112 device or disk file image
113 usedblocks Number of used space blocks on UDF disk for
115 data storage
116 freeblocks Number of free space blocks on UDF disk for
118 data storage
119 behindblocks Number of blocks which are behind the last
121 block used by UDF disk
122 numfiles Number of stored files on UDF disk
124 numdirs Number of stored directories on UDF disk
126 udfrev UDF revision needed for reading UDF disk
128 udfwriterev UDF revision needed for writing or modifying
130 UDF disk
131 vatblock UDF block location of the Virtual Allocation
133 Table (visible only when available)
134 integrity UDF integrity of Logical Volume, one of:
136 opened, closed, unknown
137 accesstype UDF Access Type, one of: overwritable,
139 rewritable, writeonce, readonly, pseudo-over‐
140 writable, unknown
141 softwriteprotect Status of UDF SoftWriteProtect flag, either yes
143 or no (available since udfinfo 2.2)
144 hardwriteprotect Status of UDF HardWriteProtect flag, either yes
146 or no (available since udfinfo 2.2)
147 When UDF integrity is not closed it means that the UDF disk was not
149 properly unmounted, is in an inconsistent state and needs repairing.
150 When either softwriteprotect or hardwriteprotect flag is set then UDF
152 disk should be treated as read-only.
153 All UDF string identifiers are stored on UDF disk in Unicode, therefore
155 they are locale or code page agnostic. Options --locale, --u8, --u16
156 and --utf8 controls how are identifiers encoded on output.
157 All newline characters from the UDF string identifiers are removed, so
159 it is guaranteed that the newline character is present only as a sepa‐
160 rator.
161 Second part of the udfinfo standard output contains list of UDF block
163 types stored on device, one per line in the following format:
164 start=block-num, blocks=block-count, type=block-type
166 With meaning that block-type starts at UDF block block-num and span
168 block-count blocks on device.
169 Windows-specific Volume Serial Number is a non-standard 32-bit check‐
171 sum, calculated as four separate 8-bit XOR checksums of 512 bytes long
172 UDF File Set Descriptor. Therefore, it cannot be set or changed as
173 opposed to UUID which is 64-bit long. This non-standard checksum is
174 used only by Windows systems (since Windows 98 era when it was intro‐
175 duced) and can be displayed on Windows systems by applications like
176 vol, dir or fsutil.exe.
177
180 udfinfo prior to version 2.2 was unable to print Unicode strings with
181 code points above U+FFFF correctly.
182 udfinfo prior to version 2.2 was unable to read Metadata Partition.
184 Therefore, determining used and free space blocks, reading File Set
185 Identifier and calculating Windows-specific Volume Serial Number did
186 not have to be available or correctly calculated for disks with UDF
187 revisions higher than 2.01 which had Metadata Partition.
188 udfinfo prior to version 2.1 was unable to read Virtual Allocation Ta‐
190 ble stored outside of Information Control Block. Therefore above limi‐
191 tation applied also for some Write Once media.
192
195 Pali Rohár <pali.rohar@gmail.com>
196
199 udfinfo is part of the udftools package since version 2.0 and is avail‐
200 able from https://github.com/pali/udftools/.
201
204 mkudffs(8), pktsetup(8), udflabel(8), cdrwtool(1), wrudf(1)
205Commands udftools UDFINFO(1)