From: Pheeef <pheeef@proton.me>
To: Lund Svein-Erik <sel@selund.se>
Cc: "Iván Méndez Cairós" <imendez@integratyc.com>,
"Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: AW: RE: Proxmox VE stretched cluster with NetApp MetroCluster over Fibre Channel
Date: Mon, 10 Aug 2026 22:25:47 +0000 [thread overview]
Message-ID: <LsAnahja40xd14I00OAO8_pvl-4BjseJt5KwJQiDf3mwWQ_tcvbBIy87KbzTFz8ZBqrrAB1MWHUHsbvOkTaMAyGuKljs7VEDzV1zxZnf57I=@proton.me> (raw)
In-Reply-To: <1795188768.63775.1785434065168.JavaMail.zextras@selund.se>
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
Hi,
Svein-Erik has already done a great job going over your questions. Only one thing to add from my side:
> 2. Is shared LVM over a multipath FC device the appropriate storage configuration for this design?
If it's `what you have` it's fine. Just make sure you make your LUNs bigger than you have in VMware, since we can only use Thick-LVM as shared storage over FC. It won't use a lot more storage since usually the SAN does dedup, but we still need that free sapce to allocate to our snapshot chains (which are still a tech preview - works fine though in production)
Furthermore I can deeply recommend getting subscriptions for your Proxmox VE, our experience with support has been extremly good, to the point where we had a patch for our issue within 48 hours. (Any other vendors would be trying to blame shift the problem onto your `non-ceritified` <insert product name here> for at least a week /j).
~ pheeef
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]
prev parent reply other threads:[~2026-08-10 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 15:42 Proxmox VE stretched cluster with NetApp MetroCluster over Fibre Channel Iván Méndez Cairós
2026-07-30 17:54 ` Lund Svein-Erik
2026-08-10 22:25 ` Pheeef [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='LsAnahja40xd14I00OAO8_pvl-4BjseJt5KwJQiDf3mwWQ_tcvbBIy87KbzTFz8ZBqrrAB1MWHUHsbvOkTaMAyGuKljs7VEDzV1zxZnf57I=@proton.me' \
--to=pheeef@proton.me \
--cc=imendez@integratyc.com \
--cc=pve-user@lists.proxmox.com \
--cc=sel@selund.se \
/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