On 9/6/19 3:21 PM, ToddAndMargo via users wrote:
On 9/5/19 3:44 AM, Samuel Sieb wrote:
On 9/4/19 10:55 PM, ToddAndMargo via users wrote:
# gzip DeadStick.[date] # creates DeadStick.[date].gz # rm DeadStick.[date]
The rm will fail because gzip removes the original file when it's finished compressing. However, the other suggestion to pipe straight through gzip (or other compression program) is better anyway.
I noticed that. I had tested it on a small png file first and it did not remove it. I bet I just did not refresh my file manager soon enough.
I am going to test the straight pipe today on my USB3 ports and see if the overhead slows down the dd enough to stop crashing dd.
Also going to test another Samsung USB flash drive on USB3 and see if dd crashes. Maybe it is my ports and not the drive. Will find out.
Thank you for the tips!
Ahh poop! (Not my "exact" word.)
# dd status=progress bs=4096 if=/dev/sdb | gzip > DeadStick.FC30.2019-09-06 34489798656 bytes (34 GB, 32 GiB) copied, 404 s, 85.4 MB/s dd: error reading '/dev/sdb': Input/output error 8425692+0 records in 8425692+0 records out 34511634432 bytes (35 GB, 32 GiB) copied, 459.17 s, 75.2 MB/s
That was on my USB 3.1 port.