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, equivalent to Latin1 (ISO-8859-1). This will
59 work only for strings which Unicode code points are below U+100.
60 --u16 Encode UDF string identifiers on output to 16-bit OSTA Com‐
63 pressed Unicode format, equivalent to UCS-2BE.
64 --utf8 Encode UDF string identifiers on output to UTF-8.
67
70 udfinfo returns 0 if successful, non-zero if there are problems like a
71 block device does not contain UDF filesystem.
72
75 First part of the udfinfo standard output contains information in
76 key=value format. List of all keys with their meaning are in the fol‐
77 lowing table:
78 filename File name of the selected block device or disk
81 file image
82 label label is an alias for lvid, see udflabel(8) sec‐
84 tion UDF LABEL AND UUID
85 uuid UUID are first 16 hexadecimal lowercase digits
87 of fullvsid, but see udflabel(8) section UDF
88 LABEL AND UUID
89 lvid UDF Logical Volume Identifier stored in UDF Log‐
91 ical Volume Descriptor
92 vid UDF Volume Identifier stored in UDF Primary Vol‐
94 ume Descriptor
95 vsid fullvsid after uuid part, typically 17.–127.
97 character
98 fsid UDF File Set Identifier stored in UDF File Set
100 Descriptor
101 fullvsid UDF Volume Set Identifier stored in UDF Primary
103 Volume Descriptor
104 winserialnum Windows-specific Volume Serial Number
106 blocksize UDF block size
108 blocks Number of all blocks on the selected block
110 device or disk file image
111 usedblocks Number of used space blocks on UDF disk for data
113 storage
114 freeblocks Number of free space blocks on UDF disk for data
116 storage
117 behindblocks Number of blocks which are behind the last block
119 used by UDF disk
120 numfiles Number of stored files on UDF disk
122 numdirs Number of stored directories on UDF disk
124 udfrev UDF revision needed for reading UDF disk
126 udfwriterev UDF revision needed for writing or modifying UDF
128 disk
129 vatblock UDF block location of the Virtual Allocation Ta‐
131 ble (visible only when available)
132 integrity UDF integrity of Logical Volume, one of: opened,
134 closed, unknown
135 accesstype UDF Access Type, one of: overwritable,
137 rewritable, writeonce, readonly, pseudo-over‐
138 writable, unknown
139 When UDF integrity is not closed it means that the UDF disk was not
141 properly unmounted, is in an inconsistent state and needs repairing.
142 All UDF string identifiers are stored on UDF disk in Unicode, therefore
144 they are locale or code page agnostic. Options --locale, --u8, --u16
145 and --utf8 controls how are identifiers encoded on output.
146 All newline characters from the UDF string identifiers are removed, so
148 it is guaranteed that the newline character is present only as a sepa‐
149 rator.
150 Second part of the udfinfo standard output contains list of UDF block
152 types stored on device, one per line in the following format:
153 start=block-num, blocks=block-count, type=block-type
155 With meaning that block-type starts at UDF block block-num and span
157 block-count blocks on device.
158 Windows-specific Volume Serial Number is a non-standard 32-bit check‐
160 sum, calculated as four separate 8-bit XOR checksums of 512 bytes long
161 UDF File Set Descriptor. Therefore, it cannot be set or changed as
162 opposed to UUID which is 64-bit long. This non-standard checksum is
163 used only by Windows systems (since Windows 98 era when it was intro‐
164 duced) and can be displayed on Windows systems by applications like
165 vol, dir or fsutil.exe.
166
169 udfinfo is not able to read Metadata Partition yet. Therefore, deter‐
170 mining used and free space blocks, reading File Set Identifier and cal‐
171 culating Windows-specific Volume Serial Number may not be available for
172 disks with UDF revisions higher than 2.01 which have Metadata Parti‐
173 tion.
174 udfinfo prior to version 2.1 was unable to read Virtual Allocation Ta‐
176 ble stored outside of Information Control Block. Therefore above limi‐
177 tation applied also for some Write Once media.
178
181 Pali Rohár <pali.rohar@gmail.com>
182
185 udfinfo is part of the udftools package since version 2.0 and is avail‐
186 able from https://github.com/pali/udftools/.
187
190 mkudffs(8), pktsetup(8), udflabel(8), cdrwtool(1), wrudf(1)
191Commands udftools UDFINFO(1)