0 Replies Latest reply: Oct 1, 2012 7:45 AM by hoppah
hoppah Level 1 Level 1 (0 points)

I maintain several Macs at home.  They all utilize files off of a NAS for various applications, and these are accessed via shares.  The shares, when active, show up in /Volumes.  AFP is the network file protocol I'm using.

 

Often, especially after a reboot, applications fail because they cannot access their files.  I find when this is the case that the original share exists in /Volumes, as, for example:

 

/Volumes/MyFileShare

 

but the applications are unable to access files via it, and there is a different share name in /Volumes which now appears to be the active mount, which is:

 

/Volumes/MyFileShare-1

 

I have to disconnect from the NAS and do a "sudo umount [AnnoyingShares]" until there are none, then reconnect to the NAS to clear these and restore the single, valid share.  Sometimes there will be a number of them, such as:

 

/Volumes/MyFileShare

/Volumes/MyFileShare-1

/Volumes/MyFileShare-2

 

et cetera.  So my question is, where are these extra mounts coming from and how do I "fix" this so that the "original" share is activated and working and the OS doesn't create the -1 or -2 duplicates?

 

H.


Mac Pro (Mid 2010), Mac OS X (10.7.2), 8-core Xeon, 16G ECC RAM, 0+1 RAID