all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Filip Schauer <f.schauer@proxmox.com>
To: Markus Frank <m.frank@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements
Date: Wed, 6 May 2026 16:03:09 +0200	[thread overview]
Message-ID: <d0578135-4b2b-448b-be54-575a60587795@proxmox.com> (raw)
In-Reply-To: <d8e8960a-0abe-4635-ae5d-ec7492995465@proxmox.com>

On 27/04/2026 17:17, Filip Schauer wrote:
> backing fs  live mig. method  data integrity  write works?  read works?
> NFS         find-paths        ok              yes           yes
> NFS         file-handles      data mismatch   yes           yes
> CephFS      find-paths        ok              yes           yes
> CephFS      file-handles      ok              yes           yes
> CIFS        find-paths        copy failed     I/O error     I/O error
> CIFS        file-handles      copy failed     I/O error     yes
>
>
> Live Migration with CephFS backing virtiofs worked flawlessly.
>
> NFS worked well with find-paths
> but with file-handles it corrupted (zeroed out) 1536 Bytes of data.

On my previous tests with NFS, my NFS share was configured as:
/mnt/mysharedir *(rw,sync)
in /etc/exports

This time I tested with `no_root_squash` (per Markus' suggestion):
/mnt/mysharedir *(no_root_squash,rw,sync)


backing fs  live mig. method  data integrity  write works?  read works?
NFS         find-paths        ok              yes           yes
NFS         find-handles      data mismatch   yes           yes


It still corrupted my data with `find-handles`. This time 1024 Bytes
were zeroed out in the target file of the `dd`.





      reply	other threads:[~2026-05-06 14:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 12:16 [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements Markus Frank
2026-04-27 12:16 ` [PATCH guest-common v3 1/11] mapping: dir: add 'live-migration-method' parameter Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 2/11] fix #6370: virtiofs: add support for thread-pool-size option Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 3/11] virtiofs: add readonly option Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 4/11] virtiofs: add live migration support Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 5/11] virtiofs: add explanation for cache=metadata behavior Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 6/11] virtiofs: add table for optional parameters Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 7/11] virtiofs: add description for thread-pool-size and readonly Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 8/11] virtiofs: add documentation for live migration Markus Frank
2026-04-27 12:16 ` [PATCH manager v3 09/11] fix #6370: ui: virtiofs edit: add support for thread-pool-size option Markus Frank
2026-04-27 12:16 ` [PATCH manager v3 10/11] virtiofs edit: add support for readonly option Markus Frank
2026-04-27 12:17 ` [PATCH manager v3 11/11] directory mapping: add live-migration-method option for virtiofs Markus Frank
2026-04-27 15:18 ` [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements Filip Schauer
2026-05-06 14:03   ` Filip Schauer [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=d0578135-4b2b-448b-be54-575a60587795@proxmox.com \
    --to=f.schauer@proxmox.com \
    --cc=m.frank@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