[Bug 1905979] Re: Check if F_OFD_SETLK is supported may give wrong result

2020-12-08 Thread Olaf Seibert
That is indeed the source and patches, but I wanted to follow their git repo for easier maintenance. Surely they must have one. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1905979 Title: Check if

[Bug 1905979] Re: Check if F_OFD_SETLK is supported may give wrong result

2020-12-08 Thread Olaf Seibert
The kernel version is Linux hostname 4.15.0-124-generic #127-Ubuntu SMP Fri Nov 6 10:54:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1905979 Title: Check

[Bug 1905979] Re: Check if F_OFD_SETLK is supported may give wrong result

2020-12-08 Thread Olaf Seibert
Interesting. Thanks for the link. The file system we are using is the Quobyte file system (2.24.1) (https://www.quobyte.com/), which works via FUSE. We've had problems with OFD locks with this file system in the past, so my first thought, seeing the error in comment #1, was that those would be

[Bug 1905979] Re: Check if F_OFD_SETLK is supported may give wrong result

2020-12-07 Thread Olaf Seibert
This is rather serious, since it causes VMs to crash: Unexpected error in raw_check_lock_bytes() at /build/qemu-PKI6mj/qemu-4.2/block/file-posix.c:796: Failed to get "write" lock 2020-11-23 11:32:27.810+: shutting down, reason=crashed when openstack attempts to create a snapshot. -- You re

[Bug 1905979] [NEW] Check if F_OFD_SETLK is supported may give wrong result

2020-11-27 Thread Olaf Seibert
Public bug reported: In util/osdep.c there is a function qemu_probe_lock_ops() to check if file locks F_OFD_SETLK and F_OFD_GETLK (of the style "Open file description locks (non-POSIX)") are supported. This test is done by trying a lock operation on the file /dev/null. This test can get a wrong

[Bug 1865048] Re: qemu-img --force-share does not disable file locking

2020-02-28 Thread Olaf Seibert
Hi Maz, thanks for the information! The situation we're in is where we are suspecting the file locking on a shared network file system to be broken, so we were looking for ways to avoid any locking. I had tried some variations on your image-opts style invocation, but did not find any variant wher

[Bug 1865048] [NEW] qemu-img --force-share does not disable file locking

2020-02-27 Thread Olaf Seibert
Public bug reported: The new option "--force-share" for qemu-img does not disable file locking. I tried it with version qemu-img version 2.11.1(Debian 1:2.11+dfsg- 1ubuntu7.21~cloud0) and I traced the source code of the current git trunk. Sample to demonstrate: # strace qemu-img info --force-sh