From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 630E460703 for ; Mon, 10 Jan 2022 20:53:50 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5AEBF6BB0 for ; Mon, 10 Jan 2022 20:53:20 +0100 (CET) Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id B45EB6BA3 for ; Mon, 10 Jan 2022 20:53:18 +0100 (CET) Received: by mail-il1-x12a.google.com with SMTP id d3so12350685ilr.10 for ; Mon, 10 Jan 2022 11:53:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=6v0MEIz1F6Ue5X2e/MntSua6fX/vj3ClJCOCr3ZW6Ww=; b=Zd3PQZAJTFfj8DkkwRyT7q0ISCP4V0zjciJN2ml8uoLK2CRp1zMRjIp7Ghejajb60R fIMkhKpapIMD6vkdPVVi4qax1pFktwc/xK5FreZYzDk1rmlAaoXnOPWZ1DGyI6LXomyc BlzMrA+B0Kw2dDICkPSHkhJIoTSZGdAasdsMPV10wEH2VHgvuCm2Ip3qJ8kfnhEcU7XF n9Odli+lA83NLRl0T+TJjT5x8Jv6aeQHqDoSdAvn3mLiOkyg+SqlEoltP7C/1DfFGy2W gNFvy3n03OLBpJngsxhIo9XPcpfJc40Am5K69j/5iNMdfgchcnsGBZLF1d0Hl8ufcBpR XNkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=6v0MEIz1F6Ue5X2e/MntSua6fX/vj3ClJCOCr3ZW6Ww=; b=vLpBXUWPs28g5u8nsDUK/q/H8k4DTA7MR/gZ/SphPeVsvHJ4+ahH/TY4CIKBWhiKsE LGe4etwIUf77gFhu5y/1RumSLwvyphcoYpW6UiETFnvra2/xzvD2Nt0zIz00EqzsH/Up l58wWguKWZ3+XYLtoIBCilOqWvQp8L+Lub6OXLNVfBFXiRKk5OjXybJTFTkDga7UOHPm w3l8jv1Ux1M0WsQH0YSvLTcEwIkW6YVEuyj1mJygg4tELrzHw29kgOAvtXBYS/e2Hlhe 9WcuX89yTQ+/am/4jvJ4/K+j401mc2nRzkkIZ70/kQuxO9KzGfJIN5ucBMt4Kj2+pG4Y 01yg== X-Gm-Message-State: AOAM533tDEDYKccGm6WWdhv6lvzn7RxMDmy+6FruEVDCkzxkdhu1rzQB m0FShtTRpMPaKvXhk1rLG6ubuWoSJGMAvaZqzaVchnh3 X-Google-Smtp-Source: ABdhPJzh95MsZT4cxJa3oclYc3Zo3MnkGc7qis694+XH5hkcEhP+Oo2aktKSKdsrIvUtfd2fl7nvtRSzJJ72eLLayAc= X-Received: by 2002:a05:6e02:12e8:: with SMTP id l8mr765289iln.111.1641844391307; Mon, 10 Jan 2022 11:53:11 -0800 (PST) MIME-Version: 1.0 References: <20220110141350.716d9727@schleppmd.hlrs.de> In-Reply-To: From: Kyle Schmitt Date: Mon, 10 Jan 2022 13:53:00 -0600 Message-ID: To: Proxmox VE user list Content-Type: text/plain; charset="UTF-8" X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Proxmox and ZFS on large JBOD ? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 19:53:50 -0000 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 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 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 > >