-
Notifications
You must be signed in to change notification settings - Fork 171
Syncing to SMB share fails #227
Comments
I'm on my phone and struggling to find the previous issue which had the
same error.
However I think SQLite does not like SMB for some reason. You can can
override the location of the DB with --db-path and put it on your local
disk. This will also improve performance.
…On Sun, 26 Apr 2020, 09:55 wally007, ***@***.***> wrote:
Assigned #227 <#227> to
@gilesknap <https://github.com/gilesknap>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#227 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHLRW244SS6PWJY5BVIMI3ROPZG3ANCNFSM4MREGJ2Q>
.
|
In Bug #221 the user got the same error as you have and it was fixed by moving the db to the local disk using the --db-path argument. I already have a known issue that NFS, SMB and CIFS file systems dont support file locks and therefore you can't place the DB on these. Yours is a subtly different error because for some reason you have got past the lock issue.. Please let me know if --db-path fixes the problem for you. |
Thank you. It worked with --db-path option (setting it to local file system) |
Thanks for letting me know. |
Describe the bug
CentOS 7.6 - running as root - using SNAP install method (pipenv method fails to install on CentOS 7.6)
Trying initial sync to SMB share fails (server is Windows 10 Pro)
Sync to local storage works
SMB permissions are correct as gphotos-sync creates .db, log, sqlite and lock file in destination (on the SMB share)
Here is the console output (tried with and without
--ntfs
flag -result is the same):here is the log file:
I'm aware that symlinks are not supported (i dont have any albums anyway) and will only sync once a month FULL Google Photos library (flush-index) - in order to always get latest version (edited) files)
The text was updated successfully, but these errors were encountered: