-
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
Must disable locking with davfs2 when using owncloud #9176
Comments
At the moment ownCloud doesn´t support WebDAV locks. Disabling them in davfs2 should be no problem |
Thanks for the explanation! Now the issue with davfs2 is clear. Yet, if ownCloud does not support WebDAV locks, IMHO one of the following two actions should be performed:
|
Just a quick note for others interested in this issue: It seems action 1 by @callegar was implemented by now. /sbin/mount.davfs: warning: the server does not support locks users: Imho no action is required on your side. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi,
I have an issue when using davfs2 to mount owncloud storage space.
Unless I disable the locking in the davfs2 configuration, I continuously get input-output errors when renaming directories.
This is very evident when using the file synchronizer 'unison' over the webdav mounts, since this synchronizer does a lot of renames.
Disabling the locking in davfs2 seems wrong, but makes everything work and also seems to make operation faster when there are many small files to be copied over the webdav mount. However, it also seems the wrong thing to do... any idea? An issue in owncloud? In sabredav? in davfs2?
Note that it is not just me having this issue. I came to trying disable the locking because I found the hint to disable the locking by googling on the net.
The text was updated successfully, but these errors were encountered: