<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Cache in qemu is none. That should be correct. This is full command :<div class=""><br class=""></div><div class="">/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 class=""><br class=""></div><div class="">-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4</div><div class="">-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5</div><div class="">-drive file=/var/lib/one//datastores/116/312/<b class="">disk.0</b>,format=raw,if=none,id=drive-virtio-disk1,cache=none</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1</div><div class="">-drive file=<a href="gluster://localhost:24007/imagestore/" class="">gluster://localhost:24007/imagestore/</a><b class="">7b64d6757acc47a39503f68731f89b8e</b>,format=qcow2,if=none,id=drive-scsi0-0-0-0,cache=none</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </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 class="">-drive file=/var/lib/one//datastores/116/312/<b class="">disk.1</b>,format=raw,if=none,id=drive-ide0-0-0,readonly=on</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0</div><div class=""><br class=""></div><div class="">-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 0.0.0.0:312,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 class=""><br class=""></div><div class="">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 class=""><div><br class=""></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 class=""></div><div>Thanks,</div><div>BR!</div><div>Martin</div><div><br class=""><blockquote type="cite" class=""><div class="">On 13 May 2019, at 09:21, Krutika Dhananjay <<a href="mailto:kdhananj@redhat.com" class="">kdhananj@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Also, what's the caching policy that qemu is using on the affected vms?</div><div class="">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 class=""><br class=""></div><div class="">-Krutika<br class=""></div></div><br class=""><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" class="">kdhananj@redhat.com</a>> wrote:<br class=""></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" class=""><div class="">What version of gluster are you using?</div><div class="">Also, can you capture and share volume-profile output for a run where you manage to recreate this issue?</div><div class=""><a href="https://docs.gluster.org/en/v3/Administrator%20Guide/Monitoring%20Workload/#running-glusterfs-volume-profile-command" target="_blank" class="">https://docs.gluster.org/en/v3/Administrator%20Guide/Monitoring%20Workload/#running-glusterfs-volume-profile-command</a></div><div class="">Let me know if you have any questions.<br class=""></div><div class=""><br class=""></div><div class="">-Krutika<br class=""></div></div><br class=""><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" class="">snowmailer@gmail.com</a>> wrote:<br class=""></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 class="">
<br class="">
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 class="">
<br class="">
> you'd have it's log on qemu's standard output,<br class="">
<br class="">
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 class="">
<br class="">
BR,<br class="">
Martin<br class="">
<br class="">
> On 13 May 2019, at 08:55, <a href="mailto:lemonnierk@ulrar.net" target="_blank" class="">lemonnierk@ulrar.net</a> wrote:<br class="">
> <br class="">
> On Mon, May 13, 2019 at 08:47:45AM +0200, Martin Toth wrote:<br class="">
>> Hi all,<br class="">
> <br class="">
> Hi<br class="">
> <br class="">
>> <br class="">
>> 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 class="">
>> 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 class="">
>> <br class="">
> <br class="">
> As far as I know this should be unrelated, I get this during heals<br class="">
> without any freezes, it just means the storage is slow I think.<br class="">
> <br class="">
>> 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 class="">
>> 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 class="">
>> <br class="">
> <br class="">
> Any chance your gluster goes readonly ? Have you checked your gluster<br class="">
> logs to see if maybe they lose each other some times ?<br class="">
> /var/log/glusterfs<br class="">
> <br class="">
> For libgfapi accesses you'd have it's log on qemu's standard output,<br class="">
> that might contain the actual error at the time of the freez.<br class="">
> _______________________________________________<br class="">
> Gluster-users mailing list<br class="">
> <a href="mailto:Gluster-users@gluster.org" target="_blank" class="">Gluster-users@gluster.org</a><br class="">
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank" class="">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br class="">
<br class="">
_______________________________________________<br class="">
Gluster-users mailing list<br class="">
<a href="mailto:Gluster-users@gluster.org" target="_blank" class="">Gluster-users@gluster.org</a><br class="">
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank" class="">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>