-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checksum issues mainly with SMB mount point + Google Drive #40809
Comments
Here is the log entry from the server:
|
Update, it seems that other users of my instance have issues with the same problem on Google Drive too. Means that this is likely a generic problem and not related to a mount point type. |
@IljaN hoijoijoi a new checksum error that was introduced in 10.12.0 (still seen in 10.12.1) ?? |
I can also see that issue on an instance with owncloud 10.12 and external SMB mounts. Please ping me, if I can deliver any logs, etc. |
I can reproduce a similar issue with an SFTP mount on 10.12.2 -- my SMB mounts work fine. |
Interestingly, this happens only for a single or at least some users on that server and I'm not sure, if this was the case at the beginning. Nevertheless, I upgraded from 10.12.0 to 12.12.2 and will observe, if it still is the case. |
I can reproduce the error in v10.12.2, too:
|
I've opened a new clean issue with a bisect for my case: #40831 |
Adding the changes of the referenced PR manually fixed the problem and syncing is possible again. Can be closed imho. |
Thanks for confirming. |
I just installed the patch and will observe, if it helps. |
I did a quick test and at least for me it works :) |
Thanks for double checking! |
Confirmed fixed in 10.13.0-rc.1 |
Pre-submission Checks
Describe the bug
The owncloud instance running 10.11 in combination of the desktop app 3.2 and all version before never had syncing issues, a recent upgrade to desktop 4.0 did not changed the following behaviour.
Problem:
Having some SMB and Google Drive mount points and post upgrading to server 10.12.0 respectively 10.12.1, syncing data fails in the following conditions, but ONLY when using SMB, works flawless with GD.
Files can be located in any folder/subfolder representing the synced SMB mountpoint:
In these conditions the issue appears:
Note that the file gets fully accepted by the backend and can be downloaded manually without any issue, but fails syncing.
When the file is NOT present in the local sync folder, you can upload it via browser and it gets synced. It is then available locally as usual
This shows up like a sync issue from the client to the server but not vice versa.
This is the SMB mount point:
Expected behavior
Files should sync to SMB mount points as before
Steps to reproduce the issue
See the bug description above
Screenshots
No response
Logs
Right click on files that failed syncing:
Locally present but should get overwritten by the server (file update via browser)
Newly added local file
Log for newly added local file
Client version number
Client:
Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
C:\Program Files\ownCloud
Server information
Server:
Additional context
The interesting thing is, that it was challenging to identify that this is a checksum issue because the client tells that the file is blacklisted. As the server has a blacklisting configuration possibility too, this was confusing. Note that there is NO server blacklisting configured!
The text was updated successfully, but these errors were encountered: