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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 1BA2171D0D for ; Mon, 27 Jun 2022 10:50:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0FA731E5DD for ; Mon, 27 Jun 2022 10:50:42 +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 90F741E5D3 for ; Mon, 27 Jun 2022 10:50:41 +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; bh=foLWeUnxPsoQY1GC3YAH6A4P3TtOLRro0awma2ZiNLw=; b=l9Tvm8Bild7qZKWUUOkZ2YO7RRnkE7XN9pAk7CRTpcxrd6vd7MBEKE7LThmnlyVGPN5K8T9AoaPPm CQOrLHmlVpwoybCAsKY6xe/lFXk7U5o38S4Fhz4fKQp3yWdXQc5V2ucbjuyRPyac4Gxa6y4NqDnjGy imrtm+Mm5ddvPGoO5pcq15sFnhiF46sQN5NXrKAQfwtozZ1oVW25Qwekdpo3ZPm766tITdddJvvURD o3XuG8wz7kCKafCmnAF7SsbG7LaA0aKuf7L9gcGZ6Ed9xI4EAuC7FIAIx3Js1udFSbKtQxPzxnvnOP YqDcTDKsIecknONwtxSjn2sepIzcJug== 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)) for pbs-devel@lists.proxmox.com; Mon, 27 Jun 2022 10:20:34 +0200 From: "Mark Schouten" To: pbs-devel Date: Mon, 27 Jun 2022 08:20:27 +0000 Message-Id: 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.047 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: [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 08:50:42 -0000 Hi, We run a few PBS servers with a lot of datastores, ZFS based. While PBS=20 can create zpools, it currently cannot create a ZFS datastore when you=20 create a datastore via the API. Currently we have a script to create users and datastores and with the=20 corresponding ZFS filesystem: 1: Create PBS user 2: Create ZFS filesystem for this user (we set the quotum here) 3: Create a ZFS filesystem for this datastore, inside the users=20 filesystem 4: Create the datastore As we=E2=80=99re going to implement PBS-as-a-service into our portal, I wou= ld=20 like to know if it=E2=80=99s feasable to make the API create a filesystem w= hen=20 you create a datastore, or is the general feeling that this should not=20 be inside PBS=E2=80=99 scope? Regards, =E2=80=94 Mark Schouten, CTO Tuxis B.V. mark@tuxis.nl