dat: Usage problems

Hi, I’m using dat cli v12.0.0 and node v4.2.6 on a local ubuntu machine and a remote debian server. I executed:

On the local machine:

Then on the remote machine:

All good. Then, while keeping the dat share command running on the local machine, on another bash tab I executed:

Then on the remote machine:

Problem…the file is not updated to the latest version.

Back on the local machine:

Bigger problem, the source folder got reverted to the previous state!

I can’t figure out the problem…any help would be much appreciated, thanks!

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 23

Most upvoted comments

Hi @joehand, I’ve done the same tests again and its working!

Sweet! Thanks for sticking with us through these replication bugs.

However, I added a couple more steps and there are still some issues. Same scenario as before: 2 machines, one running dat share on the source folder, the other with a destination folder after running dat clone.

Right now, once a file is downloaded dat marks it as downloaded and will never update it again until there is an update at the source. We weren’t really sure how to handle this situation but we should definitely provide some way to get back in sync, similar to a git reset HEAD.

We will be changing how metadata is stored soon (in files instead of a database) that will make it easier to address this. In the meantime, you can delete the database (in .dat of the destination dir) and clone again:

rm -rf /home/jamie/folder/.dat
dat clone <link> /home/jamie/folder

This will reset the metadata, index the destination directory, and download anything missing.

joehand on Feb 22, 2017