The directory name was visible in Terminal, but if I tried to cd into it, I got a message saying "Connection refused.
Eventually, with the help of the experts on the forum on this site, I found that "dns" was listed in the table of mounts that appeared in Terminal when I entered typed the df command. The dns item was listed as "map -static" which, as I understand from other posts, means that it's a mount that isn't actually mounted, but which the system has ready for mounting when needed.
After a lot of other effort, I finally discovered what was creating this phantom mount. There was a. Instead I booted into single-user mode and moved the file to another location where I could restore it if needed although I didn't need it.
After this, Find Any File started working at top speed again, and Yasu stopped reporting an error. If file utilities and directory listings seem sluggish on your system, then it may be worth looking for files that create phantom shares in the directory listed above.
The following comments are owned by whoever posted them. This site is not responsible for what they say. Thanks for reporting this. I also planned to put this info on my support page for Find Any File. Guess I can simply link to to this page now instead of having to explain it all in my own words.
If you're using a Mac OS X user account with standard privileges, then enter su - Account , where Account is the account name, to switch to an account that has administrative privileges.
Mac OS X mounts drives by default by creating a folder with the name of the drive in /Volumes and then mounting it at that point (so a drive is. Click on the volume you're trying to mount, and click the "info" button. Mount the volume, the mount point should show the path you specified.
Enter sudo dscl , then enter your Mac OS X user account password if prompted to. Thank you!
Very clear and useful, and better than my brute-force method! Search Advanced. From our Sponsor Latest Mountain Lion Hints Click here for complete coverage of Lion on Macworld. User Functions Username: Password:.
What's New in the Forums? Nano 7 - backgrounds Sometimes, however, when you attach a local hard drive, you will see that the name of the drive has a "-1" or another number appended to it.
In OS X, drives are accessed through the Finder's various locations, but on the filesystem they are given a mount point. In this directory a folder is created and given the drive's name, and is used as the access point for all files on that local filesystem. If by chance you mount two drives of the same name, because the system can't create two mount points with the same name it appends sequential numbers to new mount points as they are created, and therefore you will see the numbered drive names in the Finder.
While the numbered names for disks should only happen if there are multiple drives attached with the same name, it can happen for other reasons as well.
If you want to fully automate the process of ejecting the disk based on a partition name, this should do the trick:. DU says to repair disk and then try mounting again. December 24, at am. October 13, at pm. Featured on Meta.
Improper unmount When you eject a drive, the system should remove the mount point for the drive; however, sometimes this doesn't happen. This should open the mount points directory, and if you see any folders, aliases, or other files in the directory that have the same name as your external drive, then remove them.
Use of multiple drives of the same name without rebooting If you have multiple hard drives of the same name then the system will append a number to the end of each if they are mounted at the same time. If you then unmount the main drive, all other drives will keep their new numbered names, and will continue to do so regardless of whether they are ejected and remounted, until the system is rebooted.
This is because the system associates the mount point name with the drive device for example, "disk1" , which is then kept associated with a particular device for the remainder of the boot session. To fix this problem, just reboot the computer and the drive's name should revert back to having no number.
If drive name problems keep happening, you might consider running a general maintenance routine on the system to clear and rebuild system caches and other temporary items and settings that might be contributing to the problem.