Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Martin Toth
Hi, there is no healing operation, not peer disconnects, no readonly filesystem. Yes, storage is slow and unavailable for 120 seconds, but why, its SSD with 10G, performance is good. > you'd have it's log on qemu's standard output, If you mean /var/log/libvirt/qemu/vm.log there is nothing. I a

Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Krutika Dhananjay
What version of gluster are you using? Also, can you capture and share volume-profile output for a run where you manage to recreate this issue? https://docs.gluster.org/en/v3/Administrator%20Guide/Monitoring%20Workload/#running-glusterfs-volume-profile-command Let me know if you have any questions.

Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Krutika Dhananjay
Also, what's the caching policy that qemu is using on the affected vms? Is it cache=none? Or something else? You can get this information in the command line of qemu-kvm process corresponding to your vm in the ps output. -Krutika On Mon, May 13, 2019 at 12:49 PM Krutika Dhananjay wrote: > What

Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Martin Toth
Cache in qemu is none. That should be correct. This is full command : /usr/bin/qemu-system-x86_64 -name one-312 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e95a774e-a594-4e98-b141-9f30a3f848c1 -no-user-config -nodefaults -c

Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Andrey Volodin
as per https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds. , the informational warning could be suppressed with : "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" Moreover, as per their website : "*This message is not an error*. It is an indication that a pro

Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Andrey Volodin
what is the context from dmesg ? On Mon, May 13, 2019 at 7:33 AM Andrey Volodin wrote: > as per > https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds. > , > the informational warning could be suppressed with : > > "echo 0 > /proc/sys/kernel/hung_task_timeout_s

Re: [Gluster-users] VMs blocked for more than 120 seconds

2019-05-13 Thread Krutika Dhananjay
OK. In that case, can you check if the following two changes help: # gluster volume set $VOL network.remote-dio off # gluster volume set $VOL performance.strict-o-direct on preferably one option changed at a time, its impact tested and then the next change applied and tested. Also, gluster versi

[Gluster-users] Invitation: Gluster Community Meeting (APAC friendly hours) @ Every 2 weeks at 11:30am on Tuesday 15 times (IST) (gluster-users@gluster.org)

2019-05-13 Thread pgurusid
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Kolkata X-LIC-LOCATION:Asia/Kolkata BEGIN:STANDARD TZOFFSETFROM:+0530 TZOFFSETTO:+0530 TZNAME:IST DTSTART:19700101T00 END:STANDARD END:VTIMEZONE BEGIN:VEVENT

[Gluster-users] Updated invitation: Gluster Community Meeting (APAC friendly hours) @ Every 2 weeks from 11:30am to 12:30pm on Tuesday 15 times (IST) (gluster-users@gluster.org)

2019-05-13 Thread pgurusid
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Kolkata X-LIC-LOCATION:Asia/Kolkata BEGIN:STANDARD TZOFFSETFROM:+0530 TZOFFSETTO:+0530 TZNAME:IST DTSTART:19700101T00 END:STANDARD END:VTIMEZONE BEGIN:VEVENT