Sublime Forum

Locked folders over nfs

#1

on macOS when i open a folder over a NFS mount i intermittently see directories that are “locked” and which don’t allow me to see or search the full set of files.

For example if i run subl /path/to/project where /path is a nfs mount i frequently see the following (edited to avoid disclosing folder names)

25%20PM

Often repeated attempts to open the same directory will move the locks down a folder (i.e. instead of seeing /path/to/project/a locked, on a second attempt one level further shows /path/to/project/a/b locked

My macOS mount looks like this

mount
/dev/disk1s1 on / (apfs, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk1s2 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
/dev/disk1s5 on /private/var/vm (apfs, local, journaled, nobrowse)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
map -static on /System/Volumes/Data/path (autofs, automounted, nobrowse)
192.168.50.2:/path on /path (nfs, nosuid, noatime)

$ subl -v && sw_vers -productName && sw_vers -productVersion
Sublime Text Build 3211
Mac OS X
10.15.5
0 Likes
#2

Those aren’t locks, they’re an indication that Sublime thinks that the folder is a symlink to a folder somewhere else in the side bar. Sublime doesn’t recurse into linked folders because it’s impossible to detect if it’s going to end up scanning the same folders over and over again.

Such folders have a context menu entry that will show you what Sublime thinks it’s linked to. Some remote file systems have been known to incorrectly provide file information that confuses the duplicate detection (i.e. reporting that two folders represent the same thing when they do not).

1 Like
#3

Thank you, this follow up is very helpful. These folders are definitely not symlink but it’s helpful to know that’s what this icon represents (i had trouble googling to find out what that icon represented). The console log reports that sublime detected repeated inodes.

A slightly redacted log entry there is

scan: /path/to/a has been seen before, skipping (using inode) previous path: /path/to/b inode: 2004414194

With this information i’ll investigate if there is a way to better tune nfs so it doesn’t re-use inode numbers.

0 Likes