all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES manager/qemu-server/docs 0/3] drop writeback cache setting
Date: Tue,  8 Apr 2025 17:07:12 +0200	[thread overview]
Message-ID: <20250408150715.105253-1-f.ebner@proxmox.com> (raw)

VirtIO-fs using writeback cache seems very broken at the moment. If a
guest accesses a file (even just using 'touch'), that the host is
currently writing, the guest can permanently end up with a truncated
version of that file. Even subsequent operations like moving the file,
will not result in the correct file being visible, but just rename the
truncated one.

manager:

Fiona Ebner (1):
  ui: virtiofs edit: drop writeback checkbox

 www/manager6/qemu/VirtiofsEdit.js | 5 -----
 1 file changed, 5 deletions(-)


qemu-server:

Fiona Ebner (1):
  virtiofs: drop writeback option

 PVE/QemuServer/Virtiofs.pm | 8 --------
 1 file changed, 8 deletions(-)


docs:

Fiona Ebner (1):
  qm: virtiofs: drop writeback cache

 qm.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


Summary over all repositories:
  3 files changed, 2 insertions(+), 15 deletions(-)

-- 
Generated by git-murpp 0.5.0


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


             reply	other threads:[~2025-04-08 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 15:07 Fiona Ebner [this message]
2025-04-08 15:07 ` [pve-devel] [PATCH manager 1/3] ui: virtiofs edit: drop writeback checkbox Fiona Ebner
2025-04-08 15:07 ` [pve-devel] [PATCH qemu-server 2/3] virtiofs: drop writeback option Fiona Ebner
2025-04-08 15:07 ` [pve-devel] [PATCH docs 3/3] qm: virtiofs: drop writeback cache Fiona Ebner
2025-04-08 15:32 ` [pve-devel] applied-series: [PATCH-SERIES manager/qemu-server/docs 0/3] drop writeback cache setting Thomas Lamprecht

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=20250408150715.105253-1-f.ebner@proxmox.com \
    --to=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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal