Quote:
Originally Posted by q345
When I first (before going on this forum) tried to change directory in preferences to the something which was mount point to NAS directory, it failed to copy it. I checked the web and found other people complained about unability of sqlite to work with NAS but find no solution, so I put a question on the forum and Toddos recommended this environmental varaible settings, which worked fine for me.
|
You came in and stated that you couldn't get metadata.db onto your NAS, and toddos told you how to not do that.... Maybe we should back up and figure out what your actual problem is before solving it
I'm confused as to why you're unable to use the metadata.db on a NAS. I used mine that way for a few days with no issues.... What toddos and I were both seeing is that *OUR* NASes (which are really Windows Home Server boxes aka WHS) got mad about the metadata.db file being open all the time. I don't immediately see why a generic NAS would have any problem with the metadata.db file unless it's doing WHS's goofy file-based replication (which I believe to be fairly unique).
For WHS, it does background file replication instead of sector-level mirroring/RAID like most other implementations. For that it must have an unlocked file otherwise WHS is (rightly) concerned that it may make a bad copy - because the file is locked for writing and therefore either actively in flux or not yet been written to a coherent state.
Calibre is perfectly happy with its metadata.db right on the WHS share alongside the ebook directory, but *WHS* is unhappy because Calibre leaves the metadata.db file locked as long as it's running. (Toddos and I both also want full-time Calibre content servers running, and Kovid has said that his sqllite library has no way to open a db for read-only.) A "normal" user who stores his/her books on the NAS and opens and closes Calibre as needed (but doesn't leave it running all the time) should have no issues regardless of NAS type.
Richard