On Mon, Oct 21, 2013 at 10:22 AM, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-10-21 16:19, Cristian Rodríguez wrote:
El 21/10/13 11:10, Carlos E. R. escribió:
To me, it is a failure :-)
Understood, however it is really not.
What is exactly a short read? It is an unknown concept to me.
- -- Cheers / Saludos,
Look back at your dd output in this thread. Sometimes you have something like: cer@minas-tirith:~> time dd if=/dev/random of=sample bs=100 count=1 ; l sample ; uptime 0+1 records in 0+1 records out 17 bytes (17 B) copied, 0,0185403 s, 0,9 kB/s === That 0+1 means 0 full blocks and 1 partial block. The partial block is caused by a short read. When things go as you expect you get 1+0 in that output. That is one full bloke and 0 partial blocks. In the presence of media errors on a disk I've seen the number of partial blocks get pretty big. I suspect if you add "conv=noerror, sync", then you would still get 17 bytes of random data from /dev/random, but then dd would null fill the rest of the block. I use that arg when reading data from disk, otherwise dd will abort on the first media error. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org