Dear Maintainer, Currently Debian uses `@rootfs` as the btrfs subvolume label in the installer while Ubuntu uses `@`. Timeshift unfortunately only supports the Ubuntu convention of `@` and not `@rootfs`. You can see this in this in their README, https://github.com/linuxmint/timeshift/blob/e7fab11ae99465a8ac405981040482c9369e957a/README.md?plain=1#L109 They have two issues to include Debian compatibility with the root subvolume named `@rootfs`. https://github.com/linuxmint/timeshift/issues/157 https://github.com/linuxmint/timeshift/issues/83 The Debian installer does not support subvolume management with btrfs. You can not rename your root subvolume from `@rootfs` to `@`. To use Timeshift on Debian, you _must_ pause the installer and modify your subvolume names. This is common, and there are at least a few YouTube videos which do this (without explaining it). See this question and attached self-answer for more information, https://unix.stackexchange.com/q/752738/3285 This is a **horrible** user experience. To be clear, if you use an uninterrupted Debian install and never drop to the terminal you can not make use of the Timeshift package later. I believe Debian should patch Timeshift to support its own convention of `@rootfs`. Both of these tools should be packaged to work by default with one another, and if they can't be made to work with one another using the installers default, this package should be removed from the repository as we're not supporting end-use with our own BTRFS installer. Note, if a patch is accepted that changes this hard-coded root-label we will break installs that have changed their root-label manually (which presumably we don't support anyway). Ideally, this would be something that could be customized without user intervention with btrfs tooling.
While I agree that the issue involving Timeshift, BTRFS, and subvolumes needs to be addressed, it is important to clarify that this problem only affects the use of Timeshift with BTRFS snapshots. It does not impact the use of Timeshift with rsync. If users encounter this issue and have formatted their drive with BTRFS, they can opt to use rsync instead of BTRFS snapshots as a fallback.