From: Kyle Schmitt <kyleaschmitt@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox and ZFS on large JBOD ?
Date: Mon, 10 Jan 2022 13:53:00 -0600 [thread overview]
Message-ID: <CAO6gj4_imzk3JwYeCFnA-Cu-Q6wv45F-Ni5Kqdx=LxyiDUZqjg@mail.gmail.com> (raw)
In-Reply-To: <CAO6gj48Z0UaTWAFi8e+7aOw5hY7pndAvjF2HsVcWaF+Hc1VkGw@mail.gmail.com>
Oh, and since we're throwing around NAS flavors that support ZFS,
Xigma-NAS, which used to be NAS4Free, is free as in speech and beer,
FreeBSD based. The UI looks a little dated, but it's very solid. I
only moved away from it because I don't use any features but ZFS and
NFS.
--Kyle
On Mon, Jan 10, 2022 at 1:50 PM Kyle Schmitt <kyleaschmitt@gmail.com> wrote:
>
> I would separate it out. I'm running a moderate sized ZFS array on
> one box, with a small 10GB ethernet network dedicated to serving NFS
> from that array to my proxmox nodes. I had bonded 1G before for the
> same setup, and usually it was a non-issue, but sometimes there was a
> slowdown. With 10G no slowdown on my workloads.
>
> I haven't explored serving ZFS from linux, so mine is on FreeBSD, and
> it's rock solid.
>
> --Kyle
>
> On Mon, Jan 10, 2022 at 7:21 AM Martin Dziobek <dziobek@hlrs.de> wrote:
> >
> > 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 19:53 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
2022-01-10 19:50 ` Kyle Schmitt
2022-01-10 19:53 ` Kyle Schmitt [this message]
[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='CAO6gj4_imzk3JwYeCFnA-Cu-Q6wv45F-Ni5Kqdx=LxyiDUZqjg@mail.gmail.com' \
--to=kyleaschmitt@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