Symbol not found errors during NetBeans indexing on NAS storage

Question

NetBeans utilizes a persistent indexing system to maintain project symbols for code completion and navigation. When project files are hosted on network-attached storage (NAS), the IDE relies on the "Scan for External Changes" mechanism to synchronize the internal index with the disk.

There is an inconsistency in how the IDE detects file system changes on certain network shares, which can result in stale cache entries. This leads to false "symbol not found" errors despite the files being present and updated on the remote server.

While manually deleting the UserDir cache folder forces a full re-index, this is not a viable automated solution for large-scale projects due to the CPU and I/O overhead of the Scan-on-Startup process.

Does NetBeans provide a configuration to increase the frequency of external change scans specifically for network-mounted directories?
  Is there a documented method to trigger a targeted index refresh for a specific project without purging the entire global cache?

Tasadduq Burney · Answer

Answer to the two questions

NetBeans does not expose a separate setting to increase the scan‑frequency for network‑mounted directories only. The IDE uses a single global interval for "Scan for External Changes" that applies to all watched folders. You can adjust that interval, but it will affect local disks as well.

You can refresh the index for a single project without clearing the global cache by using the project‑level "Scan for External Changes" action or by deleting the project‑specific index folder under the UserDir cache.

Likely explanation (based on typical NAS behavior)

The NAS share may be mounted with case‑insensitive semantics (common with SMB/CIFS on Windows‑oriented servers). NetBeans assumes a case‑sensitive view, so two files that differ only in letter case map to the same underlying file, causing the indexer to miss or mis‑assign symbols.
High latency or temporary disconnects on the NAS link can interrupt the Java File API reads during parsing, producing the same "symbol not found" message even though the source is present.
Real‑time antivirus or backup software scanning the NAS share can lock files briefly, preventing NetBeans from reading them during indexing.

Confirmed facts (from NetBeans architecture)

NetBeans relies on the standard Java java.io.File API to watch for changes. On a case‑insensitive mount, distinct paths that vary only in case resolve to the same file, so the indexer may register a symbol under one name and later fail to find it under the other.
When the NAS connection stalls or times out, the parser throws FileNotFoundException or IOException, which NetBeans surfaces as a "symbol not found" error in the editor.

Steps to mitigate the issue

Adjust the global scan interval (if you tolerate more frequent checks):
- Open Tools → Options → Miscellaneous → Files.
- Increase the value of "Refresh interval (ms)" to a smaller number (e.g., 2000 ms) to poll the NAS more often.
- Click OK and restart NetBeans for the change to take effect.
Force case‑sensitive mounting (if supported):
- On Linux/macOS, mount the share with noserverino or case=yes options (depending on the NAS protocol).
- On Windows, consider using NFS with case‑sensitive client settings or create a symbolic link forest that preserves case.
After remounting, invalidate the NetBeans cache (Help → Disable Plugins then restart) and let the IDE re‑index.
Reduce interference from antivirus/backup:
- Temporarily disable real‑time scanning on the NAS share for the NetBeans project directory.
- Observe whether the symbol‑not‑found errors disappear.
- If they do, add an exclusion rule for the project folder in your antivirus/backup software.

Targeted index refresh for a single project

Via the IDE UI: Right‑click the project in the Projects window → Scan for External Changes. This updates the file watchers and re‑runs the parser for that project only.
Via cache deletion: Close NetBeans, delete the folder <UserDir>/var/cache/index/<project‑name> (or the whole index subfolder if you are unsure of the exact name), then restart NetBeans. Only that project’s index is rebuilt; other projects retain their caches.

Missing diagnostic detail that would change the recommendation

If you can confirm whether the NAS share is mounted with case‑sensitive semantics, we can decide whether to focus on remount options (case‑sensitivity) versus latency/antivirus tuning. Please verify the mount options (e.g., output of mount on Linux/macOS or the share properties on Windows) and let me know if the share is case‑sensitive.