From: Ralf Storm <ralf.storm@konzept-is.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Proxmox and ZFS on large JBOD ?
Date: Mon, 10 Jan 2022 16:59:33 +0100 [thread overview]
Message-ID: <20080b37-49dd-cc91-ceea-874f860c22db@konzept-is.de> (raw)
In-Reply-To: <20220110141350.716d9727@schleppmd.hlrs.de>
Hello Martin,
should be no problem and you can configure wait-time at startup for ZFS
to avoid timeouts, this is also described in the proxmox doku in the ZFS
chapter.
The doku for proxmox is very good, keep on it and you will be happy.
best regards
Ralf
Am 10/01/2022 um 14:13 schrieb Martin Dziobek:
> 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
>
--
Ralf Storm
Systemadministrator
next prev parent reply other threads:[~2022-01-10 16:05 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
2022-01-10 15:05 ` Adam Thompson
2022-01-10 15:59 ` Ralf Storm [this message]
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=20080b37-49dd-cc91-ceea-874f860c22db@konzept-is.de \
--to=ralf.storm@konzept-is.de \
--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