I have beets installed a debian VM and then installed open-vm-tools on the allow VMware to create shared directories with the windows10 host machine. I’ve then made two shared drives which are located in /mnt/hgfs/. “Host-Share” for where my music resides and “Beets-Library” for the beets library.
Beets can read the music fine but when it tries to write the music to the “Beets-Library” directory it will not follow any of my Paths configuration. It dumps all the files into the “Beets-Library” with odd modifications to the file names such as “.mp3.1” or only half the name of the song. If I point the library config to a local directory on the VM beets with properly build the directories specified in my Path config.
Without special privileges I can mkdir in these directories too so I’m not sure why Beets silently fails to create directories.
Very strange! I don’t see anything obviously wrong. Is there any chance this could be at the result of bugs in the VMware shared the directory driver? If beets works fine on a normal local directory, I struggle to think of any other reasonable explanation.