Re: Using davfs2

Mo B <[email protected]> writes:

> is this still the main discussion group?
> Or is it [email protected] ?

You have posted to [email protected], and it is documented to
be the project's mailinglist:

  https://urldefense.com/v3/__https://github.com/bcpierce00/unison/wiki/Mailing-Lists__;!!IBzWLUs!SxuV48GbP3ARfkMZ0GfzLduygDkOwHqBEEd8Q5UWfV9jcB_8mP2GAnjEN2qdzkzROsCsQOZiLDUSrZrQow$ 

> Or https://urldefense.com/v3/__https://github.com/bcpierce00/unison/issues__;!!IBzWLUs!SxuV48GbP3ARfkMZ0GfzLduygDkOwHqBEEd8Q5UWfV9jcB_8mP2GAnjEN2qdzkzROsCsQOZiLDWF11FQRw$  ?

Discussion, questions, and requests for help are not permitted in the
issue tracker:

  https://urldefense.com/v3/__https://github.com/bcpierce00/unison/wiki/Reporting-Bugs-and-Feature-Requests__;!!IBzWLUs!SxuV48GbP3ARfkMZ0GfzLduygDkOwHqBEEd8Q5UWfV9jcB_8mP2GAnjEN2qdzkzROsCsQOZiLDV4Vblq-w$ 

> This is unison version 2.53.7 (ocaml 4.14.2)
>
> I have an issue when using unison on a davfs2 mount. Some months or years 
> ago when using
> -fastcheck true
> I had a very fast check when nothing has changed, about several minutes. 
> Recently every unison run is very slow and loads all the ~100GB from the 
> remote server for several hours. Before, only
> -fastcheck false
> did that but now every fastcheck true does it as well. Did anything change 
> here?

I am not aware of a change, but that doesn't mean there isn't one.

> My unison configuration:
>
> #DAV_Documents.prf
> root = /home/bb
> root = /mnt/davfs/hidrive/public
> mountpoint = Documents
> path = Documents
> include DAV_Common
>
> #DAV_Common.prf
> log = true
> perms = 0
> dontchmod = true
> links = false
> fastcheck = yes
> confirmbigdel = true
> maxthreads = 1
> ignore = Name *.part
> ignore = Name .*.swp
> ignore = Name .~lock.*
>
> # /etc/davfs2/davfs2.conf
> minimize_mem    1
> cache_size      128000               # MiByte
> table_size      262144              # 2^18
> delay_upload    2
> gui_optimize    1
> use_compression 1

I haven't used davfs2 (seems to be Linux only?).

It's possible this is due to a change within davfs2, your OS, your DAV
server, and of course within unison.  You can perhaps examine update
logs and try older versions.   It's also possible that the archive files
aren't getting stored correctly, or are not persisting.

I would suggest using ktrace/strace/ktruss (or however your operating
system spells that) to see what system calls unison is making.

Greg

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].