From: Lorne Guse via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"m.carrara@proxmox.com" <m.carrara@proxmox.com>
Cc: Lorne Guse <boomshankerx@hotmail.com>
Subject: [pve-devel] How does proxmox handle loss of connection / reboot of iSCSI storage
Date: Fri, 26 Sep 2025 02:06:13 +0000 [thread overview]
Message-ID: <mailman.417.1758853305.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 10496 bytes --]
From: Lorne Guse <boomshankerx@hotmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, "m.carrara@proxmox.com" <m.carrara@proxmox.com>
Subject: How does proxmox handle loss of connection / reboot of iSCSI storage
Date: Fri, 26 Sep 2025 02:06:13 +0000
Message-ID: <DM6PR17MB34665CA6AB7E651E1675C791D01EA@DM6PR17MB3466.namprd17.prod.outlook.com>
RE: TrueNAS over iSCSI Custom Storage Plugin
TrueNAS has asked me to investigate how Proxmox reacts to reboot of the storage server while VMs and cluster are active. This is especially relevant for updates to TrueNAS.
>The one test we'd like to see work is reboot of TrueNAS node while VMs and cluster are operational… does it it "resume" cleanly? A TrueNAS software update will be similar.
I don't think the storage plugin is responsible for this level of interaction with the storage server. Is there anything that can be done at the storage plugin level to facilitate graceful recovery when the storage server goes down?
--
Lorne Guse
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-09-26 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.417.1758853305.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=boomshankerx@hotmail.com \
--cc=m.carrara@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.