Re: [Tracker] Disable indexing on NFS

[Philip Van Hoof <philip codeminded be>]

Martyn Russell schreef op 16/09/2013 18:46:

[cut]

> > ps. If writing a patch to detect NFS mount points, the patch shouldn't
> > make it impossible to do so. As scanning NFS mount points ought to be a
> > possible use-case.
>
> The question is really whether we consider ANY mount point. Currently 
> we index all mount points separately but we also coalesce them, e.g. 
> if we have:
>
>   /media/a
>   /media/b
>
> both should be indexed. However, if we have:
>
>   /media/a
>   /media/a/nfs-mounted-location/
>
> The second of the two should be consolidated into the first because 
> it's a parent of the second.
>
> That's all fine - but what I think is happening here is we are 
> indexing $HOME and there is an nfs mount in $HOME/foo perhaps? It's 
> also quite possible that people mount other file system types in 
> $HOME/bar, etc. So the question becomes: do we want to have an option 
> to stay on the same file system or not - that should cover all NFS and 
> other file system type cases.
>
> Thoughts?

I agree. No immediate thoughts from me on this. I'm guessing that if the 
indexer is handling both right, the second pass over files of $HOME/foo 
should cooperatively work against the first pass and the other way 
around. But it's not ideal that a second pass happens in the first 
place. I'm guessing some level of detecting this at configuration 
parsing or at another later location in the FS miner wouldn't be the 
worst idea.

Kind regards,

Philip