Summary: | app-misc/tracker-0.8.17 (full) re-indexing on every login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kete Tefid <ketetefid> |
Component: | Current packages | Assignee: | Freedesktop bugs <freedesktop-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | sergey.zolotorev, z23 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 334427 |
Description
Kete Tefid
2010-10-05 17:02:21 UTC
Did you check this is not actually just checking files mtimes for example. I sure known it's not wiping it's database since content scanned on my nfs mounts are still in the db even when they are not mounted. I wish to confirm: I have the same issue with app-misc/tracker-0.8.17 and panel applet shows "File System 1%" every time after login. It seems it scans every file on FS, not only changed. I'm going to enable verbose logging and see what it doing. I've found a very strange warning in tarcker debug output: (tracker-miner-fs:12072): Tracker-WARNING **: Could not add monitor for path:'/home/serzh/Documents/books.all/Catalog_GOST/Catalog/Data/65/6573' 07 Окт 2010, 14:30:15: Tracker: Generating mtime cache for URI 'file:///home/serzh/Documents/books.all/Catalog_GOST/Catalog/Data/65/6573' (tracker-miner-fs:12072): Tracker-DEBUG: Generating mtime cache for URI 'file:///home/serzh/Documents/books.all/Catalog_GOST/Catalog/Data/65/6573' 07 Окт 2010, 14:30:15: Tracker: Populated mtime cache with '2' items (tracker-miner-fs:12072): Tracker-DEBUG: Populated mtime cache with '2' items Adding INotify watch:: No space left on device There is a lot of messages about "Adding INotify watch:: No space left on device". About which device tracker said? May be this warning a root of issue? All devices contain enough space. Hmm, '32768' in /proc/sys/fs/inotify/max_user_watches has fixes warning about 'No space left on device' but trackerd reindexes all files on every login. It's a shame that tracker-0.8.15 was just removed from the portage tree. I think 0.8.17 is unusable because of this bug. (In reply to comment #5) > It's a shame that tracker-0.8.15 was just removed from the portage tree. I > think 0.8.17 is unusable because of this bug. > I had to unmerge tracker...and now I have to use locate to find something among millions of files... Please report a bug upstream and paste the URL here. Afaik, the problem is still manifesting with tracker-0.9/master, ebuilds to test this are in tree so you can test easily whatever upstream asks you to do, even if they don't support 0.8 anymore. The files are not actually re-indexed but checked for modifications on every startup (by default). I guess upstream is unlikely to modify this behavior. |