The associated forum post URL from https://forum.rclone.org

Tried to sign up for the forum, but have not received any activation emails (I am using Gmail).

What is the problem you are having with rclone?

With a mounted webdav storage, write back after vfs-write-back also updates modtime of files.

To be specific, I was editing a text file in a mounted webdav storage. Say I saved the file at time T.
Right now the modtime locally was correct, i.e., T.

After around 5m (I suppose it was dir-cache-time), the local modtime became T+5s.
I think it was the "write back" that has changed the modtime on Webdav, because the default vfc-write-back is 5s.
This updated modtime appeared locally after dir-cache-time.

I am not sure whether this behavior is expected or a bug, but in my use case, this leads to the following problem.

I continue to make more modification of the file and try to save it at some time after T+5m.
The editor then warns me that the file on disk has changed since my last save.
I think this is because the recorded time of last save by the editor is T, while the modtime of the file on disk now becomes T+5s.

From my point of view (maybe naive), the true modtime of the file should be T. T+5s is due to the write cache, which does not represent the time when the file was last modified.

If this is not a bug, could you suggest some workarounds?
Thanks!

What is your rclone version (output from rclone version)

1.68.1

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

archlinux 64bit

Which cloud storage system are you using? (e.g. Google Drive)

Webdav

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

mounted with Options=rw,_netdev,args2env,vfs_cache_mode=full

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.