0

When specifying an output file without specifying a logfile, the output file will be truncated anyway.

How exactly is using ddrescue -t /dev/devicename outfile functionally different from ordinarily specifying an output file?

The only way ddrescue -t (or ddrescue --truncate) is different is that when trying to specify a logfile, ddrescue responsds with:

ddrescue: Outfile truncation and logfile input are incompatible.
  • 2
    From the ddrescue online manual: "Ddrescue does not write zeros to the output when it finds bad sectors in the input, and does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps without wiping out the data already rescued." So how did you arrive at the conclusion in the first sentence? – Olorin Mar 8 at 5:16
  • @Olorin Thanks. I arrived at that conclusion because I tested it. Both ways clobber the file. – neverMind9 Mar 8 at 18:48
  • @Olorin But it wipes out the data already rescued if I do not specify a logfile, therefore no difference, as far as I can think of. – neverMind9 Mar 8 at 19:47
  • 1
    What test did you use? How did you know it wiped out data already rescued? – Olorin Mar 10 at 15:49
  • @Olorin It did only wipe test data. I tested it by running both commands for 5 seconds, and the file size was approximately the same in both case. So it must have been rewritten. – neverMind9 Mar 11 at 0:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.