diff options
| author | Bartosz Taudul <wolf@nereid.pl> | 2022-12-03 04:07:24 +0300 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2022-12-05 13:50:44 +0300 |
| commit | 7868f93006ad27c00ecddcc2904118aa705459ca (patch) | |
| tree | 738672c8eb621cd4b395e8bbf27d75277ba67697 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | b41b98e12a954c306e8eb9527ada0a70db339683 (diff) | |
| download | linux-7868f93006ad27c00ecddcc2904118aa705459ca.tar.xz | |
udf: Increase UDF_MAX_READ_VERSION to 0x0260
Some discs containing the UDF file system are unable to be mounted,
failing with the following message:
UDF-fs: error (device sr0): udf_fill_super: minUDFReadRev=260
(max is 250)
The UDF 2.60 specification [0] states in the section Basic Restrictions
& Requirements (page 10):
The Minimum UDF Read Revision value shall be at most #0250 for all
media with a UDF 2.60 file system. This indicates that a UDF 2.50
implementation can read all UDF 2.60 media. Media that do not have a
Metadata Partition may use a value lower than #250.
The conclusion is that the discs failing to mount were burned with a
faulty software, which didn't follow the specification. This can be
worked around by increasing UDF_MAX_READ_VERSION to 0x260, to match the
Minimum Read Revision. No other changes are required, as reading UDF
2.60 is backward compatible with UDF 2.50.
[0] http://www.osta.org/specs/pdf/udf260.pdf
Signed-off-by: Bartosz Taudul <wolf@nereid.pl>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions