On Mon, Dec 1, 2014 at 1:39 PM, Andrei Mikhailovsky <andrei@xxxxxxxxxx> wrote:
> Ilya,
>
> I will try doing that once again tonight as this is a production cluster and
> when dds trigger that dmesg error the cluster's io becomes very bad and I
> have to reboot the server to get things on track. Most of my vms start
> having 70-90% iowait until that server is rebooted.
>
> I've actually checked what you've asked last time i've ran the test.
>
> When I do 4 dds concurrently nothing aprears in the dmesg output. No
> messages at all.
>
> The kern.log file that i've sent last time is what I got about a minute
> after i've started 8 dds. I've pasted the full output. The 8 dds did
> actually complete, but it took a rather long time. I was getting about 6MB/s
> per dd process compared to around 70MB/s per dd process when 4 dds were
> running. Do you still want me to run this or is the information i've
> provided enough?
How long did it take for all dds to complete?
Can you send the entire kern.log for that boot? I want to look at how
things progressed during the entire time dds were chunking along.
Thanks,
Ilya
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
