u/painful8th

I've got my main desktop switched from Windows 10 to Arch with some subvolumes, Suse-like and snapper based. This is a single NVMe drive with the btrfs subvolumes living inside a LUKS partition. All subvolumes are mounted with the nodiscard option and I'm running fstrim weekly via a systemd timer.

So far I have encountered no issues, but I'm wondering how I should check the health of these subvolumes. Any advice would be appreciated.

Basically title. This has been going now for some months and I'm wondering whether it has been disabled by Trakt or whether it's something I misconfigured on Umbrella and POV. IIRC I did not change anything, but I definitely can't get it to work.

Platform is LibreELEC latest if that helps.

I think I've seen some references that just leaving unallocated space on silicon storage allows its controller to do what would be otherwise be needed by running TRIM periodically.

What's your take on it?

Just wondering here since I have a couple of installs using Samsung NVMEs. And not sure whether this is something all brands do or not.

Finally, dual-mode (either Android or iOS) trackers have started appearing, namely the Ugreen finetrack duo (https://www.amazon.de/-/en/UGREEN-FineTrack-Tracker-Android-Charging/dp/B0FRLWSGPW) as well as the Xiaomi smarttag (https://www.amazon.de/-/en/XIAOMI-Smart-Tracker-IP67-Battery-Pack-4/dp/B0GSZ7LDKT).

I'm using a couple of Mototags which have a 6- to 9-month battery life, but also have (tricky at times) UWB, as well some POS Militags; totally worthless.

The Xiaomi list for the double the price. They also offer firmware upgrades while on the Apple network but not on Google's FMD one. Additionally, they have replaceable batteries (started hating this part), whereas the Ugreen are rechargable over USB-C.

Has anyone used either or both for some time to offer some real-life operation insight?