Justin Piszcz wrote:
On Thu, 17 Jan 2008, Al Boldi wrote:
Justin Piszcz wrote:
On Wed, 16 Jan 2008, Al Boldi wrote:
Also, can you retest using dd with different block-sizes?
I can do this, moment..
I know about oflag=direct but I choose to use dd with sync and
measure the
total time it takes.
/usr/bin/time -f %E -o ~/$i=chunk.txt bash -c 'dd if=/dev/zero
of=/r1/bigfile bs=1M count=10240; sync'
So I was asked on the mailing list to test dd with various chunk sizes,
here is the length of time it took
to write 10 GiB and sync per each chunk size:
4=chunk.txt:0:25.46
8=chunk.txt:0:25.63
16=chunk.txt:0:25.26
32=chunk.txt:0:25.08
64=chunk.txt:0:25.55
128=chunk.txt:0:25.26
256=chunk.txt:0:24.72
512=chunk.txt:0:24.71
1024=chunk.txt:0:25.40
2048=chunk.txt:0:25.71
4096=chunk.txt:0:27.18
8192=chunk.txt:0:29.00
16384=chunk.txt:0:31.43
32768=chunk.txt:0:50.11
65536=chunk.txt:2:20.80
What do you get with bs=512,1k,2k,4k,8k,16k...
Thanks!
--
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
root 4621 0.0 0.0 12404 760 pts/2 D+ 17:53 0:00 mdadm
-S /dev/md3
root 4664 0.0 0.0 4264 728 pts/5 S+ 17:54 0:00 grep D
Tried to stop it when it was re-syncing, DEADLOCK :(
[ 305.464904] md: md3 still in use.
[ 314.595281] md: md_do_sync() got signal ... exiting
Anyhow, done testing, time to move data back on if I can kill the
resync process w/out deadlock.
So does that indicate that there is still a deadlock issue, or that you
don't have the latest patches installed?
--
Bill Davidsen <davidsen@xxxxxxx>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
