Re-enabled unconditional reporting of MD5 tags with -check_media
This commit is contained in:
@ -9,7 +9,7 @@
|
||||
.\" First parameter, NAME, should be all caps
|
||||
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
.\" other parameters are allowed: see man(7), man(1)
|
||||
.TH XORRISO 1 "Version 1.5.1, Oct 08, 2018"
|
||||
.TH XORRISO 1 "Version 1.5.1, Nov 01, 2018"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -4663,6 +4663,12 @@ supposed to be ok but stem from a suspicious neighborhood.
|
||||
The former is a strong confirmation for quality, the latter only tells that
|
||||
one or more blocks of the region must be wrong.
|
||||
.br
|
||||
By default bad_limit is set higher than md5_mismatch, so that mismatches are
|
||||
classified as quality class "0" rather than "\-". This means that the sectors
|
||||
of a MD5 mismatch range are recorded in the sector_map as successfully read,
|
||||
if the drive handed them out at all. Set "bad_limit=md5_mismatch" to let the
|
||||
sector_map record the whole mismatching range as yet not retrieved.
|
||||
.br
|
||||
\fBslow_limit=threshold\fR
|
||||
sets the time threshold for a single read chunk to be considered
|
||||
slow. This may be a fractional number like 0.1 or 1.5.
|
||||
|
Reference in New Issue
Block a user