Zotero and shared folders on Linux virtual machine
I'm a long term Zotero user on Windows 10. I don't sync to the cloud - i.e. I keep everything local in the default directory, C:\Users\user\Zotero, with my attachments in C:\Users\user\Zotero\Storage.
I have a Linux virtual machine running in VMware Player in Windows 10. The Linux guest can share folders with the Windows host, so I can access C:\Users\user\Zotero on the Windows host as /home/user/Zotero on the Linux guest.
I've installed Zotero in the Linux guest and confirmed that /home/user/Zotero is the default location it expects.
However, in Edit/Preferences/Advanced/Files and Folders/Show Data Directory, I can see the Zotero subfolders as normal except that, in place of .../Storage, there is a folder called .../pipes which contains a single file of 0 bytes and a long numerical name.
I can see .../Storage (and its subfolders) on the Linux file system, but Zotero can't.
What have I done wrong?
I have a Linux virtual machine running in VMware Player in Windows 10. The Linux guest can share folders with the Windows host, so I can access C:\Users\user\Zotero on the Windows host as /home/user/Zotero on the Linux guest.
I've installed Zotero in the Linux guest and confirmed that /home/user/Zotero is the default location it expects.
However, in Edit/Preferences/Advanced/Files and Folders/Show Data Directory, I can see the Zotero subfolders as normal except that, in place of .../Storage, there is a folder called .../pipes which contains a single file of 0 bytes and a long numerical name.
I can see .../Storage (and its subfolders) on the Linux file system, but Zotero can't.
What have I done wrong?
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Upgrade Storage
It could also just be some issue with folder sharing.
But what bwiernik says in general — I would strongly discourage accessing the data directory across a VM boundary. You're very likely to corrupt your database or run into other problems. And we can't really provide support for this kind of unusual setup.