Is anyone aware of a way to get Spotlight to index a google drive mount?
I'm up to several thousand files at this point, so spotlight is becoming increasingly appealing/necessary.
There was an earlier thread on this but it was closed due to inactivity.
(That user referenced "Google Drive File System" but I think they maybe meant file stream? Unsure of what they were referring to...)
Getting rclone to mount to /Volumes like other MacFUSE apps would be a step in the right direction, as most guides are for network filesystems mounted in that location, but I can't make this work either. As I can't use mdutil on an individual folder, the fact that it is broken when I try to run it on what the filesystem sees as, e.g.
I've had some success with using the Commander One file manager app. It's not the same as a spotlight index, but at minimum my Google Drive (crypt) is now searchable.
What I gleaned from their docs is that spotlight will not index volumes not mounted under /Volumes
I don't think it's possible for rclone to do that. Mojave will not allow a directory to persist in /Volumes unless it was put there by the system (i.e. not created with mkdir /Volumes/rclonemountpoint).
So unless there's a way to make that happen... I don't think mdutil will work in this instance.
That said, it would be cool if rclone could mount to /Volumes ha.
Yeah, the fuse option local totally fixes it but you do need to run cache-mode writes as well:
textere@seraph bin % sudo ./rclone cmount gcrypt: /Volumes/Test --allow-other -o local
2019/11/23 11:48:49 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/0.indexIds: WriteFileHandle: Truncate: Can't change size without --vfs-cache-mode >= writes
2019/11/23 11:49:04 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/psid.db: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2019/11/23 11:49:10 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/indexState: WriteFileHandle: Can't open for write without O_TRUNC on existing file without --vfs-cache-mode >= writes
2019/11/23 11:49:10 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/psid.db: WriteFileHandle: Can't open for write without O_TRUNC on existing file without --vfs-cache-mode >= writes
2019/11/23 11:49:10 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/psid.db: WriteFileHandle: Can't open for write without O_TRUNC on existing file without --vfs-cache-mode >= writes
2019/11/23 11:49:10 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/0.indexIds: WriteFileHandle: Truncate: Can't change size without --vfs-cache-mode >= writes
2019/11/23 11:49:16 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/psid.db: WriteFileHandle: Can't open for write without O_TRUNC on existing file without --vfs-cache-mode >= writes
2019/11/23 11:49:16 ERROR : .Spotlight-V100/Store-V2/4DD496ED-DF24-43E7-8E02-F1027EA2DCAB/psid.db: WriteFileHandle: Can't open for write without O_TRUNC on existing file without --vfs-cache-mode >= writes
Is what I see when I check the mount:
gcrypt: on /Volumes/Test (osxfuse, local, synchronous)