[SOLVED] dd looped itself or stuck

smsware · 2014-04-11 13:00:47

I went

sudo dd bs=4M if=x86_64.iso of=/dev/sdb && sync

and it's working 12 hours now... I don't think it should be like that and

sudo kill -USR1 6331

does nothing, no output about current state. Still, my USB stick is blinking like it's being written. I don't want to stop it as I don't want to wait another day if it's all right and just takes a lot of time... or should I? What could be the reason?

Edit: well, I've turned it off, it was 100M remaining... my bad but now I know it actually can be THAT slow. ;-)

Last edited by smsware (2014-04-11 14:03:38)

karol · 2014-04-11 14:23:54

12 minutes is way too long and 12 hours ...
Is it USB3, USB2 or USBzero? ;-)

WonderWoofy · 2014-04-11 14:49:50

@smsware, instead of using the "&& sync" afterwords you can simply use

# dd if=/path/to/archiso of=/dev/sdb bs=4m conv=fdatasync,fsync

dd man page wrote:

fdatasync
physically write output file data before finishing
fsync
likewise, but also write metadata

smsware · 2014-04-11 16:12:03

karol wrote:

12 minutes is way too long and 12 hours ...
Is it USB3, USB2 or USBzero? ;-)

Just some random USB stick with commercial on it, have no idea.

@WonderWoofy: how it that simpler? More to remember. ;-)

WonderWoofy · 2014-04-11 23:14:45

Just thought I would mention it. There is a big range of things you can do with the conv= parameter. So I figured just knowing that section existed would be good. Additionally, I don't know that you need to use both fsync and fdatasync, as fsync is for metadata only. I imagine using fdatasync alone would ensure that it gets written fine since that is the bulk of the writes.

Arch Linux

#1 2014-04-11 13:00:47

[SOLVED] dd looped itself or stuck

#2 2014-04-11 14:23:54

Re: [SOLVED] dd looped itself or stuck

#3 2014-04-11 14:49:50

Re: [SOLVED] dd looped itself or stuck

#4 2014-04-11 16:12:03

Re: [SOLVED] dd looped itself or stuck

#5 2014-04-11 23:14:45

Re: [SOLVED] dd looped itself or stuck

Board footer