Add a New Comment (Rich Markup)
To get more information about what is going on I ask you to do this:
After some time again mount the file system (but keep the cache directory unchanged), copy the same file, unmount and create a file with log messages and the output of ls -l. Attach both files to this item. The HTTP-messages in the log files together with the directory listing of the cache directory should show why davfs2 downloads the file a second time. Werner
I set my cache size, umounted/remounted: $ grep -i cache_size .davfs2/davfs2.conf cache_size 5000000 # MiByte But, as soon as I umounted... traveled.. and remounted, the cache seemed to be flushed. More investigation shows this: Find a file in cache: username@hmm:~$ ls .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-FocswZ -l -rw------- 1 username username 3923394 Jan 14 18:06 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-FocswZ Access/view file with image program. Delay/bandwidth shows that the file is downloaded... I now look at atime, and also notice a new copy of the file: username@hmm:~$ ls -l --time=atime .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-* -rw------- 1 username username 3923394 Mar 18 08:13 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-FocswZ -rw------- 1 username username 3923394 Mar 20 05:33 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-Vp4bPg So, it didn't access the cached file at all. username@hmm:~$ ls -l --time=ctime .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-* -rw------- 1 username username 3923394 Mar 18 08:13 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-FocswZ -rw------- 1 username username 3923394 Mar 20 05:33 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-Vp4bPg mtime: username@hmm:~$ ls -l .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-* -rw------- 1 username username 3923394 Jan 14 18:06 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-FocswZ -rw------- 1 username username 3923394 Jan 14 18:06 .davfs2/cache/remoteurl.host-remote.php-dav-files-username+home-username-DAVFS2+username/IMG_20200114_1539037.jpg-Vp4bPg What I don't get, is other instances (like the nextcloud Android client), can tell when files have been updated. Is there any way I can help debug what's up here? Any suggestions on checking to see if something is non-compliant in nextcloud's webdav implementation? Any davfs2 output I can provide to help here? Thanks
Just set option cache_size high enough. Your WebDAV server must of course comply to the specs. It must not send wrong information about the modification date and the etag of the file. "I know, from many of the issues/reports I've read, that the thought in mind is 'save space!'" This was never the intention of davfs2. It is an error of some users of davfs2. Please see the README file. Werner
I know that davfs2 was developed with one usage case in mind. However, I ask that other usage cases are taken into account. Mine? I want it all. I have a nextcloud server, with webdav. I have an android phone, using the nextcloud client, and another with a webdav client. And, I have my desktop and laptop. And disk space is completely irrelevant in my case. I mean, I take photos with my Android device, and I just want them all on my desktop. Always. Without re-downloading ever. I want a perpetual, 'forever' cloned dir. And I want to save a file, anywhere, and have the file constantly on my device. I know, from many of the issues/reports I've read, that the thought in mind is 'save space!', and that there are concerns about using all the space on a device. Yet, all of my devices have 100s of gigs free. If they ever get near full, I could free space. And my webdav is a mere 20G. And yup.. I want that 20G taking up space on every davfs2. Can you add options to 'never expire cache, ever'? And, '100TB is just fine as a cache size' or some such? Because I really, really am not concerned about saving space. I know this may not be the main usage case, but these days, with android devices + nextcloud and such, I bet lots of people would like this...
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 3 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.11