From: Adam Thompson <athompso@athompso.net>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
"pve-user@pve.proxmox.com" <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] Proxmox and ZFS on large JBOD ?
Date: Mon, 10 Jan 2022 14:32:19 +0000 [thread overview]
Message-ID: <YT2PR01MB46220CAED920E87D3DF3C342AB509@YT2PR01MB4622.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220110141350.716d9727@schleppmd.hlrs.de>
IMHO, you want TrueNAS, not Proxmox, to solve this problem.
Ultimately, the problem is SystemD's notion of dependencies and timeouts, which Proxmox+OpenZFS still relies on.
Source: I have a Debian 10 system with 29 storage devices, 24 of which are multipathed, and have had to edit & override various systemd settings to get it to boot cleanly, reliably.
-Adam
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: pve-user <pve-user-bounces@lists.proxmox.com> on behalf of Martin Dziobek <dziobek@hlrs.de>
Sent: Monday, January 10, 2022 7:13:50 AM
To: pve-user@pve.proxmox.com <pve-user@pve.proxmox.com>
Subject: [PVE-User] Proxmox and ZFS on large JBOD ?
Hi pve-users !
Does anybody has experiences if proxmox works
flawlessly to manage a large zfs volume consisting
of a SAS-connected JBOD of 60 * 1TB-HDDs ?
Right now, management is done with a regular
Debian 11 installation, and rebooting the thing
always ends up in a timeout mess at network startup,
because it takes ages to enumerate all those member disks,
import the zpool and export it via NFS.
I am considering to install Proxmox on this server for the
sole purpose of smooth startup and management operation.
Might that be a stable solution ?
Best regards,
Martin
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2022-01-10 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 13:13 Martin Dziobek
2022-01-10 14:32 ` Adam Thompson [this message]
2022-01-10 15:05 ` Adam Thompson
2022-01-10 15:59 ` Ralf Storm
2022-01-10 19:50 ` Kyle Schmitt
2022-01-10 19:53 ` Kyle Schmitt
[not found] ` <YT2PR01MB46220CAED920E87D3DF3C342AB509@yt2pr01mb4622.canprd01.prod.outlook.com>
2022-01-20 13:16 ` Daniel Plominski
2022-02-04 12:39 ` Martin Dziobek
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=YT2PR01MB46220CAED920E87D3DF3C342AB509@YT2PR01MB4622.CANPRD01.PROD.OUTLOOK.COM \
--to=athompso@athompso.net \
--cc=pve-user@lists.proxmox.com \
--cc=pve-user@pve.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.