You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a cloud that shares a large music folder using external mount to a complete group. In the past, I was able to exclude this folder from the indexing by creating a .noindex file accordingly. This feature seems to be gone in the meantime.
The problem is that the indexing of the complete music archive (>300GB, >50,000 files, counting is just running) multiplied by the number of users having access to the external storage results in such a huge number of files that indexing takes days to weeks. Currently, the index is somehow broken. I try to figure out what the problem is but I cannot get it as each testing iteration takes so incredibly long.
Was there a 9good) reason for removing this very handy feature?
The text was updated successfully, but these errors were encountered:
I have a cloud that shares a large music folder using external mount to a complete group. In the past, I was able to exclude this folder from the indexing by creating a
.noindex
file accordingly. This feature seems to be gone in the meantime.The problem is that the indexing of the complete music archive (>300GB, >50,000 files, counting is just running) multiplied by the number of users having access to the external storage results in such a huge number of files that indexing takes days to weeks. Currently, the index is somehow broken. I try to figure out what the problem is but I cannot get it as each testing iteration takes so incredibly long.
Was there a 9good) reason for removing this very handy feature?
The text was updated successfully, but these errors were encountered: