disk path changes resulted in the Anytxt index becoming invalid

[plsz]

My computer system is Fedora 42, and there are two NVMe disks, each with multiple partitions. After a recent restart, I noticed that Anytxt was using a high amount of CPU, as if it were rebuilding its index. When I checked the Anytxt index directory, I found that the index was labeled using device names, such as dev.nvme0n1p4.atc . However, the system sometimes swaps the order of nvme0 and nvme1 during boot, causing the index to lose correspondence with the partitions. Is it possible to use UUIDs, similar to blkid, to associate the partitions instead?

[Abbie]

Hello.

Thank you for your suggestion, we will consider this plan.

[Author]

Posts