https://bugs.kde.org/show_bug.cgi?id=515572
--- Comment #10 from [email protected] --- (In reply to Daniel from comment #8) > All media is stored on NAS, previously mounted with "cifs smb". .... > I've found that the main problem is because of the smb shares. Inodes are > changing on every restart of the system. Even DeviceIDs are not really > fixed. I'm using NFS now, which is more stable, but still sometimes do > change DeviceIDs. If observed inodes change on each restart/remount then Baloo is not the right tool for the job :-/ It *should* be that Baloo digs down and finds the Filesystem ID rather than device number. It used to use device numbers and that's what caused the trouble with BTRFS, that was patched a while back. Indexing ought to be done local to the data and a client do the query over the net. That's a utopian ideal though. > As an alternative I've installed "nemo" on my Ubuntu KDE System. > Nemo gets the media information from "mediainfo" and does not require > indexing. It's much more reliable. You could also try recoll which gives a wide range of controls that Baloo holds in the background. -- You are receiving this mail because: You are watching all bug changes.
