<div dir="ltr"><div dir="ltr"><div><br></div>what is the context from <span style="color:rgb(36,39,41);font-family:Consolas,Menlo,Monaco,"Lucida Console","Liberation Mono","DejaVu Sans Mono","Bitstream Vera Sans Mono","Courier New",monospace,sans-serif;font-size:13px;white-space:pre-wrap;background-color:rgb(239,240,241)">dmesg </span>?</div><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 13, 2019 at 7:33 AM Andrey Volodin <<a href="mailto:andrevolodin@gmail.com">andrevolodin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">as per <a href="https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds." target="_blank">https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds.</a> , the informational warning could be suppressed with :<div><pre style="font-family:monospace,Courier;padding:0.6em 1em;border:1px dashed rgb(47,111,171);color:rgb(0,0,0);background-color:rgb(249,249,249);line-height:1.1em;border-radius:0.3em;font-size:12.7px">"echo 0 > /proc/sys/kernel/hung_task_timeout_secs"</pre></div></div>Moreover, as per their website : "<b style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.7px">This message is not an error</b><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.7px">.<br></span><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.7px">It is an indication that a program has had to wait for a very long time, and what it was doing.</span><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.7px"> </span>"<div>More reference: <a href="https://serverfault.com/questions/405210/can-high-load-cause-server-hang-and-error-blocked-for-more-than-120-seconds" target="_blank">https://serverfault.com/questions/405210/can-high-load-cause-server-hang-and-error-blocked-for-more-than-120-seconds</a></div><div><br></div><div>Regards,</div><div>Andrei<br><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 13, 2019 at 7:32 AM Martin Toth <<a href="mailto:snowmailer@gmail.com" target="_blank">snowmailer@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Cache in qemu is none. That should be correct. This is full command :<div><br></div><div>/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 -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-312/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot order=c,menu=on,splash-time=3000,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 </div><div><br></div><div>-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4</div><div>-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5</div><div>-drive file=/var/lib/one//datastores/116/312/<b>disk.0</b>,format=raw,if=none,id=drive-virtio-disk1,cache=none</div><div><span class="gmail-m_862868196881881996gmail-m_-3617246215483808938Apple-tab-span" style="white-space:pre-wrap"> </span>-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1</div><div>-drive file=<a>gluster://localhost:24007/imagestore/</a><b>7b64d6757acc47a39503f68731f89b8e</b>,format=qcow2,if=none,id=drive-scsi0-0-0-0,cache=none</div><div><span class="gmail-m_862868196881881996gmail-m_-3617246215483808938Apple-tab-span" style="white-space:pre-wrap"> </span>-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0</div><div>-drive file=/var/lib/one//datastores/116/312/<b>disk.1</b>,format=raw,if=none,id=drive-ide0-0-0,readonly=on</div><div><span class="gmail-m_862868196881881996gmail-m_-3617246215483808938Apple-tab-span" style="white-space:pre-wrap"> </span>-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0</div><div><br></div><div>-netdev tap,fd=26,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=02:00:5c:f0:e4:39,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-one-312/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -vnc <a href="http://0.0.0.0:312" target="_blank">0.0.0.0:312</a>,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on</div><div><br></div><div>I’ve highlighted disks. First is VM context disk - Fuse used, second is SDA (OS is installed here) - libgfapi used, third is SWAP - Fuse used.<br><div><br></div><div>Krutika,</div><div>I will start profiling on Gluster Volumes and wait for next VM to fail. Than I will attach/send profiling info after some VM will be failed. I suppose this is correct profiling strategy.</div><div><br></div><div>Thanks,</div><div>BR!</div><div>Martin</div><div><br><blockquote type="cite"><div>On 13 May 2019, at 09:21, Krutika Dhananjay <<a href="mailto:kdhananj@redhat.com" target="_blank">kdhananj@redhat.com</a>> wrote:</div><br class="gmail-m_862868196881881996gmail-m_-3617246215483808938Apple-interchange-newline"><div><div dir="ltr"><div>Also, what's the caching policy that qemu is using on the affected vms?</div><div>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.</div><div><br></div><div>-Krutika<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 13, 2019 at 12:49 PM Krutika Dhananjay <<a href="mailto:kdhananj@redhat.com" target="_blank">kdhananj@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>What version of gluster are you using?</div><div>Also, can you capture and share volume-profile output for a run where you manage to recreate this issue?</div><div><a href="https://docs.gluster.org/en/v3/Administrator%20Guide/Monitoring%20Workload/#running-glusterfs-volume-profile-command" target="_blank">https://docs.gluster.org/en/v3/Administrator%20Guide/Monitoring%20Workload/#running-glusterfs-volume-profile-command</a></div><div>Let me know if you have any questions.<br></div><div><br></div><div>-Krutika<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 13, 2019 at 12:34 PM Martin Toth <<a href="mailto:snowmailer@gmail.com" target="_blank">snowmailer@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
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.<br>
<br>
> you'd have it's log on qemu's standard output,<br>
<br>
If you mean /var/log/libvirt/qemu/vm.log there is nothing. I am looking for problem for more than month, tried everything. Can’t find anything. Any more clues or leads?<br>
<br>
BR,<br>
Martin<br>
<br>
> On 13 May 2019, at 08:55, <a href="mailto:lemonnierk@ulrar.net" target="_blank">lemonnierk@ulrar.net</a> wrote:<br>
> <br>
> On Mon, May 13, 2019 at 08:47:45AM +0200, Martin Toth wrote:<br>
>> Hi all,<br>
> <br>
> Hi<br>
> <br>
>> <br>
>> I am running replica 3 on SSDs with 10G networking, everything works OK but VMs stored in Gluster volume occasionally freeze with “Task XY blocked for more than 120 seconds”.<br>
>> Only solution is to poweroff (hard) VM and than boot it up again. I am unable to SSH and also login with console, its stuck probably on some disk operation. No error/warning logs or messages are store in VMs logs.<br>
>> <br>
> <br>
> As far as I know this should be unrelated, I get this during heals<br>
> without any freezes, it just means the storage is slow I think.<br>
> <br>
>> KVM/Libvirt(qemu) using libgfapi and fuse mount to access VM disks on replica volume. Can someone advice how to debug this problem or what can cause these issues? <br>
>> It’s really annoying, I’ve tried to google everything but nothing came up. I’ve tried changing virtio-scsi-pci to virtio-blk-pci disk drivers, but its not related.<br>
>> <br>
> <br>
> Any chance your gluster goes readonly ? Have you checked your gluster<br>
> logs to see if maybe they lose each other some times ?<br>
> /var/log/glusterfs<br>
> <br>
> For libgfapi accesses you'd have it's log on qemu's standard output,<br>
> that might contain the actual error at the time of the freez.<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>
</blockquote></div>
</div></blockquote></div><br></div></div>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div></div></div></div>
</blockquote></div></div>