0

According to this answer it should not be performing like this but here it is doing exactly that!

Screenshot of DDRESCUE showing performance metric

Giacomo1968
  • 55,001
  • 1
    dd could be skipping zeroed or TRIMed areas of disk. What kind of disk are you copying from or to? Otherwise it could be using caching: https://unix.stackexchange.com/questions/691372/dd-faster-than-it-should-be – Mokubai Jan 01 '24 at 17:47
  • 5
    please do not post a picture of text ... copy and paste the text instead – jsotola Jan 01 '24 at 17:47
  • 2
    What kind of SATA drive is this? (Specifically, why does it say "non-tried: 9223 petabytes")? – u1686_grawity Jan 01 '24 at 18:02
  • 1
  • It’s not skipping trimmed areas

  • Sorry

  • It’s copying from /dev/zero to an raid array. The source of this strangeness was BTRFS compression. The huge size reported by ddrescue was a result of it being unable to read the size of the fake file

  • – FennecTECH Jan 01 '24 at 23:10