From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
by lore.proxmox.com (Postfix) with ESMTPS id 0FF771FF173
for <inbox@lore.proxmox.com>; Mon, 13 Jan 2025 15:29:23 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id AE77818EA;
Mon, 13 Jan 2025 15:29:06 +0100 (CET)
Date: Mon, 13 Jan 2025 15:28:56 +0100
To: pve-devel@lists.proxmox.com
References: <AS8PR09MB4645CECB0A5AA527E14305E5E81C2@AS8PR09MB4645.eurprd09.prod.outlook.com>
In-Reply-To: <AS8PR09MB4645CECB0A5AA527E14305E5E81C2@AS8PR09MB4645.eurprd09.prod.outlook.com>
MIME-Version: 1.0
Message-ID: <mailman.267.1736778546.441.pve-devel@lists.proxmox.com>
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
From: Fabio Fantoni via pve-devel <pve-devel@lists.proxmox.com>
Precedence: list
Cc: Fabio Fantoni <fabio.fantoni@m2r.biz>
X-Mailman-Version: 2.1.29
X-BeenThere: pve-devel@lists.proxmox.com
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
Subject: Re: [pve-devel] better BTRFS integration
Content-Type: multipart/mixed; boundary="===============7611008232828077591=="
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
--===============7611008232828077591==
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <fabio.fantoni@m2r.biz>
X-Original-To: pve-devel@lists.proxmox.com
Delivered-To: pve-devel@lists.proxmox.com
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 B562ACC75F
for <pve-devel@lists.proxmox.com>; Mon, 13 Jan 2025 15:29:05 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 9FA371929
for <pve-devel@lists.proxmox.com>; Mon, 13 Jan 2025 15:29:05 +0100 (CET)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636])
(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
for <pve-devel@lists.proxmox.com>; Mon, 13 Jan 2025 15:29:04 +0100 (CET)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-aaf8f0ea963so857513066b.3
for <pve-devel@lists.proxmox.com>; Mon, 13 Jan 2025 06:29:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=m2r-biz.20230601.gappssmtp.com; s=20230601; t=1736778538; x=1737383338; darn=lists.proxmox.com;
h=content-transfer-encoding:in-reply-to:from:references:to
:content-language:subject:user-agent:mime-version:date:message-id
:from:to:cc:subject:date:message-id:reply-to;
bh=sEsQvKcxQ2HSP6pdR1BKiwyqCjERmziwclSH2zM98J4=;
b=Qk8kY6rxGzvJo5AJ+GE524hJocUrAf1f7RqNAw1stkZbBFCgUPlq6CgJSJ2v0jC92J
zhAkzNxIkuyBffba6osruKBxnrM/7bkPQ3af2tCdeHMiYsY3j/B+3QJbLlA8nZNg34Uw
bk2SknofJTUyZObcHu5mmqNKNeiQgTunKMuIlrt/in78Hwrl/w0UbkDtn2BL63RHIu+9
k4kNRoLeHZCXDJsPOscEZQcNWpvWHuE5L9YcXTLM72V+ylox2U4Pw6Lg1tQRLA+3Ua+L
qYV/MxBZDZObGxqaZQg6MgX7ZY5iphDEb10De2YmBzrp0i04KowtubTT/9W/RDv7IHug
G24Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1736778538; x=1737383338;
h=content-transfer-encoding:in-reply-to:from:references:to
:content-language:subject:user-agent:mime-version:date:message-id
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=sEsQvKcxQ2HSP6pdR1BKiwyqCjERmziwclSH2zM98J4=;
b=ueua6xiY2Ut/tE5PQl/Yp3hZzNfWJj1pUq0KMA20cdtWVO2TCXQBKOU3Iqyr8awNWZ
xycwKv4utXY24CnmeQTUPCr2ILP6r3chwkenV93AHR1myaVzwB8FeFFDVvHcdQ196rkh
WwU5KDv24iKFuWLP49a0Wowq0+fu7m8snRnRbWa9t0GYAIcbLTiMRCea58my3bUcTZHC
v1NPFEe+GvMQS8Wmk3xbB16bhtPQbF5yEfdoPeUBTCX4RD06POsz7J7tv4gMKzRz16NW
CHzsOZIBf/M3xSgapXJRpM22JRkRYmlEncGCowpepG9hrItNr19GRCvwQJsU4DvAZOer
z1Cg==
X-Gm-Message-State: AOJu0YwKmDNZeJk3+oAUxW4nZiU51SZdMsdF3sf9bVml8xZRfwDjQx+E
ZtXeoruUeA/WXL1BU1T6DusMjqW0SSW+wdaq3W30HdQTYEWab+coUg3YPs+e7YGSyFRTjO83SOk
m
X-Gm-Gg: ASbGnctzvGblN0Psv92dEOyRz1eCrcrx90MuEOv4KR6ZUCgfru8o1ZVsHPW7WSzeDM3
JSccYZbfVZsUJRTVzlkG4vuXglGBR+2x4MyH/NQqHY8MYsRENzEPz3Uc4ZixSeVu24XEHuXElVo
jd1m4sdPVqt2yhAsLb8rzLbzHYmKyHJ0aIhJmbVXsE5er2qOasHuj1GjrXc6KyqqX4CzYC00gHz
AnpSZibqSet8x49EdBYQBsUXD8qXSYM2/qGmvpkL5y5K3cPpmWCalReF73eXITTzSFFZHxaKj+a
RdhUwxiSL6HVqPo8VGkyNNplsAAL/67x/REdh4XT0ryQjfw=
X-Google-Smtp-Source: AGHT+IH6CxbIO5GzyNMhdIL5HtI7BJ1KkHgIrY3XCdikegjxqgSw2bIc+i9ljCCWWBQeZDEOoy4VnQ==
X-Received: by 2002:a17:907:7f1e:b0:aa6:7091:1e91 with SMTP id a640c23a62f3a-ab2ab66cf8cmr2037349166b.11.1736778538209;
Mon, 13 Jan 2025 06:28:58 -0800 (PST)
Received: from [192.168.178.27] (host-79-16-223-149.retail.telecomitalia.it. [79.16.223.149])
by smtp.googlemail.com with ESMTPSA id a640c23a62f3a-ab2c9060533sm509558366b.23.2025.01.13.06.28.57
for <pve-devel@lists.proxmox.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Mon, 13 Jan 2025 06:28:57 -0800 (PST)
Message-ID: <8067514a-d751-4df7-b127-fb97c371ec53@m2r.biz>
Date: Mon, 13 Jan 2025 15:28:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [pve-devel] better BTRFS integration
Content-Language: it
To: pve-devel@lists.proxmox.com
References: <AS8PR09MB4645CECB0A5AA527E14305E5E81C2@AS8PR09MB4645.eurprd09.prod.outlook.com>
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
In-Reply-To: <AS8PR09MB4645CECB0A5AA527E14305E5E81C2@AS8PR09MB4645.eurprd09.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: Avast (VPS 250113-2, 13/1/2025), Outbound message
X-Antivirus-Status: Clean
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.083 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
DMARC_PASS -0.1 DMARC pass policy
JMQ_SPF_NEUTRAL 0.5 SPF set to ?all
KAM_INFOUSMEBIZ 0.75 Prevalent use of .info|.us|.me|.me.uk|.biz|xyz|id|rocks|life domains in spam/malware
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
Il 10/01/2025 13:20, Udo Rader ha scritto:
> Hi,
>
> I have been using PVE with BTRFS as root on some nodes for some time now and all in all it seems to work quite well. What is missing, however, is a deeper integration into the user interface, for example.
>
> Browsing through the ML archives, I see that every now and then something has been done to fix minor BTRFS issues and add features, but as far as I can tell, no further attempts have been made recently to fully integrate it into the UI and/or backend API.
>
> Although I'm no BTRFS expert, I'm still tempted to improve this situation by adding the necessary code for the user interface and backend. I have contributed a few things in the past, such as the ISCSI ILO plugin, so I am generally familiar with the PVE sources, though not really in detail anymore. What I would like, for example, would be an integration into the UI + API as for ZFS, i.e. at least the display of existing BTRFS devices, profiles etc., but ideally of course also the creation and editing of existing BTRFS profiles.
>
> But before I jump into it, I'd like to know if anyone else has worked on this or is currently working on this, as there's no point in duplicating work. Or maybe it's on the roadmap for the next version anyway :D
>
> BR Udo
Thanks for wanting to help improve btrfs support, currently
unfortunately very limited, from what I've seen unfortunately there has
been little interest from developers (or I'm wrong?), so I think any
help is useful, I'm also using btrfs on system disks and storage for iso
and other data while I use lvmthin for vm disks (I use all ssd/nvme
customers level disks).
Before implementing new things in the interface I think there are some
more important things to fix/improve first, some of which I already
tried to write something about.
For example efi boot support on multiple disks
(https://bugzilla.proxmox.com/show_bug.cgi?id=5433), currently only done
at creation, one possibility would be to use proxmox-boot-tool and do
what it already does on zfs but having the entire /boot in the ESP
partition does not seem optimal to me and I have seen many posts on the
forum of failed updates due to full space for several kernel versions,
if you really wanted to do it you would have to increase the size of the
partition to limit such problems as much as possible.
I saw that Ubuntu has implemented multiple ESP management (for the
resilient boot project) over 4 years ago but asking the Grub team on
Debian why it was not applied there too, they told me that it should be
re-implemented better, avoiding code duplication, before it can be
accepted on Debian (which requires higher quality) so I don't know if
and when it will be done.
Then unfortunately I noticed a limited support for btrfs also from
Debian, for several packages unfortunately it seems that their
maintainers are inactive (not only for those but also for other packages
that they maintain), even if I don't have much time to maintain other
packages I kept an eye on some, for btrfs-progs which is essential
another maintainer took over since the previous one was confirmed MIA,
so basic support still seems guaranteed for Debian 13.
I wanted to see about packaging btdu which would be very useful even
though I have no experience with the D language but unfortunately at the
moment there is a lack of support even for basic compilation packages
for D due to the main maintainer being inactive, I'm keeping an eye on
it and writing to unblock the situation and then maybe I'll try to see
if I can package btdu.
About proxmox another thing useful would be improve the subvolumes on
the install:
https://forum.proxmox.com/threads/btrfs-subvolumes.120055/#post-722177
At the interface level one thing that could be improved is perhaps the
management or even just additional warnings to avoid a problem using vm
disks on btrfs that must not have cache=none if cow is active:
https://bugzilla.proxmox.com/show_bug.cgi?id=5320
Regarding having more information about btrfs volumes in the interface I
think it could be useful, even if those with a bit of experience can do
it in a simple and fast way, having some information in the interface
would be faster anyway, while performing any delicate operations making
it too simple in some cases would risk increasing the risks that
inexperienced users cause problems but since even more complex and
delicate things are already implemented in other parts it could be done
later also with btrfs.
Do you already have in mind how to do it and what?
> ________________________________
>
> Udo Rader, MSc, MBA, Chief Geek
> BestSolution.at EDV Systemhaus GmbH
> Salurner Straße 15, 6020 Innsbruck, Austria
> https://www.BestSolution.at
> Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
> [BestSolution]
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
--
Questa email è stata esaminata alla ricerca di virus dal software antivirus Avast.
www.avast.com
--===============7611008232828077591==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
--===============7611008232828077591==--