From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 qemu-server] fix #4099: disable io_uring for virtual disks on CIFS storages
Date: Fri, 28 Oct 2022 10:18:17 +0200 [thread overview]
Message-ID: <be83400b-1588-34f9-a28a-c1781ef8e94b@proxmox.com> (raw)
In-Reply-To: <20221027071345.12661-1-f.ebner@proxmox.com>
On 27/10/2022 09:13, Fiona Ebner wrote:
> Since kernel 5.15, there is an issue with io_uring when used in
> combination with CIFS [0]. Unfortunately, the kernel developers did
> not suggest any way to resolve the issue and didn't comment on my
> proposed one. So for now, just disable io_uring when the storage is
> CIFS, like is done for other storage types that had problematic
> interactions.
>
> It is rather easy to reproduce when writing large amounts of data
> within the VM. I used
> dd if=/dev/urandom of=file bs=1M count=1000
> to reproduce it consistently, but your mileage may vary.
>
> Some forum reports about users running into the issue [1][2][3].
>
> [0]: https://www.spinics.net/lists/linux-cifs/msg26734.html
> [1]: https://forum.proxmox.com/threads/109848/
> [2]: https://forum.proxmox.com/threads/110464/
> [3]: https://forum.proxmox.com/threads/111382/
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes from v1:
> * Add 'fix #4099'-prefix to commit title.
>
> PVE/QemuServer.pm | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
>
really unfortunate indeed though, a kernel fix would be nicer,
but there's only so much time we can spent waiting on progress
there, so ...
applied, thanks!
prev parent reply other threads:[~2022-10-28 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 7:13 [pve-devel] " Fiona Ebner
2022-10-28 8:18 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be83400b-1588-34f9-a28a-c1781ef8e94b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.