https://bugs.kde.org/show_bug.cgi?id=471289
--- Comment #5 from Nate Graham <n...@kde.org> --- Git commit 7a1c09ed1b7aa9a7a093f8d715b42a4aedd0f7b6 by Nate Graham, on behalf of Tomáš Trnka. Committed on 07/09/2023 at 17:54. Pushed by ngraham into branch 'kf5'. Use the FSID as the device identifier where possible The device number returned by stat() in st_dev is not persistent in many cases. Btrfs subvolumes or partitions on NVMe devices are assigned device numbers dynamically, so the resulting device ID is typically different after every reboot, forcing Baloo to repeatedly reindex all files. Fortunately, filesystems like Btrfs or ext4 return a persistent unique filesystem ID as f_fsid from statvfs(), so we can use that when available. Other filesystems like XFS derive the FSID from the device number of the underlying block device, so switching to the FSID does not change anything. Related: bug 402154 (cherry picked from commit c735faf5a6a3ef3d29882552ad0a9264a294e038) M +21 -1 src/engine/idutils.h https://invent.kde.org/frameworks/baloo/-/commit/7a1c09ed1b7aa9a7a093f8d715b42a4aedd0f7b6 -- You are receiving this mail because: You are watching all bug changes.
