This is weird & hard to explain, but I'll try:

Mint 20.1

This desktop has NFS mounts that come from a Synology Disk Station. Almost everything is visible using Nemo (File Manager), but recently some subdirectories and their contents have disappeared from the normal display. The subdirectories and files do exist on the server, I can see them via ssh and I can see their Samba mounts on a Windows computer on this same network. It's only some specific files, on this desktop, that do not show in the normal File Manager display.

I can get to the files by typing the entire path and filename into the address bar at the top of the Nemo window.

I have restarted both the server and client. I reinstalled Nemo, purged Nemo and installed it.

Any suggestions?

Not really, without knowing what those directories are called or more details. And since it's NFS related, it could be permissions-related. Typically, it's either permissions or what the directory is called.

Most file managers will hide files/folders that begin with a dot, i.e. .filename or .foldername and if you want them displayed, you can toggle display of dotfiles/hidden files in your menu or often with CTRL+H.

So does the file/folder you're talking about begin with a dot? If not, a screenshot of `ls -l` and `nemo` in the same folder might lend some clues....

Thanks for the replies. As often happens to me, in the process of writing the description of the problem, I found something else. When I list the problem directory with the CLI, using "ls," I see an error "ls: reading directory '.': Too many levels of symbolic links." I didn't notice this before ... so that's a rabbit to chase before I waste any more of your time. Let me see what I can find out. I'll try to post results soon.

OK, well: I pursued that error message and found a total of 3 symbolic links in the entire mount. Don't know what they were doing there or how they got made, but they are gone now and the thing is working as it should. I think there are 2 general possibilities: (1) inadvertent unintended command executed with fat fingers, or (2) my rather old Synology Disk Station may be demented. It may be time to look at that box, but for now I'll wait and see if this happens again.

My sincere thanks for your responses and I hope that I may be able to return the favor, or, as they say, "pay it forward."

Please mark thread as solved.