From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] pve wiki docs wrong -- shared zfs via iscsi isn't possible
Date: Thu, 29 Feb 2024 20:24:08 +0100 [thread overview]
Message-ID: <0fe68fd5-1d64-428e-889b-c5ec6eb24860@gmail.com> (raw)
In-Reply-To: <mailman.318.1709233855.434.pve-user@lists.proxmox.com>
I think "shared" is used in the sense of "can be accessed from different hosts" but not "simultaniously".
Like every other block device that is available over the network it is up to the file system to coordinate
simultaniously access. ZFS is unable to do so. But that doesn't mean that it cannot be used from different hosts (at
different times).
So this depends on your POV whether ZFS over iSCSI is "shared". But technically "shared: true" is right.
Am 29.02.24 um 20:05 schrieb Roland via pve-user:
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next parent reply other threads:[~2024-02-29 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.318.1709233855.434.pve-user@lists.proxmox.com>
2024-02-29 19:24 ` Uwe Sauter [this message]
[not found] ` <mailman.319.1709241604.434.pve-user@lists.proxmox.com>
2024-03-01 7:36 ` Dominik Csapak
[not found] ` <f8439578-5390-452f-8165-9efa6b32e9c1@web.de>
2024-03-01 8:22 ` Dominik Csapak
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=0fe68fd5-1d64-428e-889b-c5ec6eb24860@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=pve-user@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