Bug#678015: of blockdev-wipe
I think this is just a bug in blockdev-wipe and whatever it's
stdout is wired to.
I ran into the same situation testing di-beta1 on a KVM guest; and was
seeing only 6MB/s during the erase stage running blockdev-wipe.
Given that blockdev-wipe is only writing 0's anyway, I tried dd instead,
and dd manages >100MB/s
I suspect the problem here is that blockdev-wipe is being too
eager outputting progress information to something that's
then taking time to consume it.
Given that dd is on the image anyway, I suggest using that instead,
and if you want a progress indicator then watch /proc/??/fd/? of the
dd process; I also suggest using a larger blocksize.
Note this also corresponds to Ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/945001
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ gro.gilbert @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
Reply to: