From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/3] ui: virtiofs edit: drop writeback checkbox
Date: Tue, 8 Apr 2025 17:07:13 +0200 [thread overview]
Message-ID: <20250408150715.105253-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20250408150715.105253-1-f.ebner@proxmox.com>
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.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
www/manager6/qemu/VirtiofsEdit.js | 5 -----
1 file changed, 5 deletions(-)
diff --git a/www/manager6/qemu/VirtiofsEdit.js b/www/manager6/qemu/VirtiofsEdit.js
index fe8dc930..6983a763 100644
--- a/www/manager6/qemu/VirtiofsEdit.js
+++ b/www/manager6/qemu/VirtiofsEdit.js
@@ -57,11 +57,6 @@ Ext.define('PVE.qemu.VirtiofsInputPanel', {
['never', 'never'],
],
},
- {
- xtype: 'proxmoxcheckbox',
- name: 'writeback',
- fieldLabel: gettext('Writeback cache'),
- },
{
xtype: 'proxmoxcheckbox',
name: 'expose-xattr',
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent 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 [pve-devel] [PATCH-SERIES manager/qemu-server/docs 0/3] drop writeback cache setting Fiona Ebner
2025-04-08 15:07 ` Fiona Ebner [this message]
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-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal