Naziel a écrit
4) (Third phase; Scraping)
Donc l'option -c ne sert pas dans ce cas je pense (en tout cas pour cette phase).
J'allais dire "En effet", mais, sauf erreur de ma part, on est dans la phase précédente :
3) (Second phase; Trimming) Trimming is done in one pass. For each non-trimmed block, read forwards one sector at a time from the leading edge of the block until a bad sector is found. Then read backwards one sector at a time from the trailing edge of the block until a bad sector is found. Then mark the bad sectors found (if any) as bad-sector, and mark the rest of the block as non-scraped without trying to read it. If any edge is already adjacent to a bad sector, it is considered as already trimmed and is not trimmed again.
non ?
Ou alors dans la phase "Retrying" ?
5) (Fourth phase; Retrying) Optionally try to read again the bad sectors until the specified number of retry passes is reached. The direction is reversed after each pass.
.
- -
.
Naziel a écritmais -R et -d [?]
Pour -d,
Si je comprends bien,
`-d'
`--direct'
Use direct disc access to read from INFILE, bypassing the kernel
cache. (Open the file with the O_DIRECT flag). Use it only on
devices or partitions, not on regular files. Sector size must be
correctly set for this to work. Not all systems support this.
If your system does not support direct disc access, ddrescue will
warn you. If the sector size is not correctly set, all reads will
result in errors, and no data will be rescued.
le kernel n'approfondit pas en cas d'erreur de lecture d'un secteur, alors que -d permet d'entrer dans le détail du secteur.
Encore une fois,
si je comprends bien.
Pour -R,
`-R'
`--reverse'
Reverse direction of copying, retrying, and the sequential part of
splitting, running them backwards from the end of the input file.
Mais ce soir, je n'y vois plus clair. 🙁
