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 1F26671D2F for ; Mon, 27 Jun 2022 12:14:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 158481F61A for ; Mon, 27 Jun 2022 12:14:38 +0200 (CEST) Received: from kerio.tuxis.nl (alrami.saas.tuxis.net [31.3.111.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 9C96D1F611 for ; Mon, 27 Jun 2022 12:14:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tuxis.nl; s=mail; h=from:reply-to:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=Ni1Tb6fhs91YL05DmK7u8C1QupflN/4iMeqz68Q5CGA=; b=mbzQNlvTwIhLM1TW1l3YQjV51+G0j0uAP4Z/OGTl2PfdHbAcFP+c+/v1FAMy+D1XIWF2GwT+Z7Fhu GfWUzTizpTQI8SzsyxM2KZMQwmCqZIxkLA94QrQyH7tfs4hiBCa+9NJKpCg5XTyknB+JaA2hbM/vVF I2U9gvLDQitsR/YfbMg5zrualj5D6xVrZl++n6g0FwrhX13BqI7GjU1vMG2JLZ50X0nY0HM6IDNS4C HJOHGIhdrSmdm/hG2InAE+1Thh3kGjFvTjFfQwWbT4MU08MSnpMguGYNGgcHbHcLSFiCpBWZg+kIF7 Ffj+PJ0HLMShAZjKSTywFepfabM7mPQ== X-Footer: dHV4aXMubmw= Received: from [IPv6:2a03:7900:64::1000] ([2a03:7900:64::1000]) (authenticated user mark@tuxis.nl) by kerio.tuxis.nl (Kerio Connect 9.4.1) with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Mon, 27 Jun 2022 12:14:37 +0200 From: "Mark Schouten" To: "Dominik Csapak" , "Proxmox Backup Server development discussion" Date: Mon, 27 Jun 2022 10:14:30 +0000 Message-Id: In-Reply-To: References: Reply-To: "Mark Schouten" User-Agent: eM_Client/9.0.1755.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.042 Adjusted score from AWL reputation of From: address 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pbs-devel] Create a ZFS filesystem upon datastore creation X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2022 10:14:38 -0000 Hi, >imo is that the wrong point for such things, since the datastore creation >only takes an (arbitrary) path, which has really nothing to do with >the underlying filesystem. > >we already have a zpool creation in the api/gui, maybe we could extend tha= t >to also be able to create (and destroy?) zfs fs? That would be a big win. What I=E2=80=99m trying to prevent is that we need = to=20 create a second API-tool on PBS-servers to handle the ZFS interaction. =E2=80=94 Mark Schouten, CTO Tuxis B.V. mark@tuxis.nl