I've just spent hours fixing a problem that appears to have been caused due to OS X spontaneously changing volume names for network volumes. I am running OS X 10.6.1. I have an SMB mapped network share that houses all of the media files I use on the Mac. For example, all of my music files are on this SMB share, and in the Library.XML file I can see that the Mac refers to all of them as having the location of; file://localhost/Volumes/Music And in the terminal I can see this volume mapped as; //Jason@gizmo:139/Music (gizmo is the name of the server). The problem is that in a recent iTunes library copy operation which involved exporting of playlists, etc, I observed that I was missing a LARGE amount of music. Investigation showed that I had a large number of tracks that had the file path of file://localhost/Volumes/Music-1 Sure enough when I did a df command on the terminal I could see that for all of my network shares I had mappings for both the original volume name as well as a 2nd mapping that referred to that same volume with "-1" tacked onto the end of it. A reboot got rid of the duplicate volumes but leaves me with the question of "how the hell does this happen"? I would hate to copy a bunch of new music into iTunes from this network share only to discover that the same thing has happened again.