Hi, has there been any news on this in the last few years gone by?I've been using btrfs on debian for about ten years now, I use it both personally on some data volumes and backups and at work on servers for backups, data and root of some servers (but without snapshots for each on the root volumes).
I'm about to try to start using it seriously also with roots and snapshots for my new workstation and on future servers but I'm finding that the support on debian is unfortunately very limited, requires more time and additional operations and also difficult to reuse existing volumes while maintaining the data.
the ability to manage btrfs subvolumes at installation would be a great thing that would allow having an installation with the necessary subvolumes in a much simpler and faster way and also to use existing volumes (without having to move the content, create temporary partitions etc...)
another good thing for server will be also RAID support, I saw this related to RAID1 opened ten years ago here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748724
another useful thing, would be to have some options that can be set during installation, mainly compression (being able to choose whether to enable it and with which option), you can easily convert it afterwards but these are additional operations. Other can be for example set single/duplicate profile for data/metadata.
In any case thanks for your work and thanks for the minimal subvolume support that was added.
in case you can't make support subvolumes settable in the installer for Debian 13 could it be quite simple and fast to at least have a choice to create only minimal (like now) or "extended" subvolumes?
for extended I think can be added for example:- /var/log: both to keep them for debugging in case of root rollback and for the numerous writes on them (which would unnecessarily impact root snapshots) - /var/cache and /var/tmp: contain temporary files and caches. for don't waste space on root snapshot. - /var/spool: Contains data that is awaiting some kind of later processing, such as mail, mail queues, printing, printer spool, and so on. To prevent the loss of mail, printing, and spool data following a rollback.
there are also other that can be specific to some usage, I don't know if good have them by default on extended, for example:
- /var/lib/libvirt/images: The default location for libvirt-managed virtual machine images. So that virtual machine images are not replaced with older versions during a rollback.
- /var/www: Web server directory. To keep hosted web server data separate and prevent data loss during system root rollbacks.
have more subvolume like these easy/fast on install I think will decrease issues for many users that will use root snapshot and rollback, without good knowledgedoing them manually after the installation
thanks for any reply and sorry for my bad english
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature