Deleting files on temporary network dropouts

------=_Part_801170_528114627.1767955611931
Content-Type: multipart/alternative; 
	boundary="----=_Part_801171_1520203165.1767955611931"

------=_Part_801171_1520203165.1767955611931
Content-Type: text/plain; charset="UTF-8"

Coming from https://github.com/bcpierce00/unison/issues/989 ...

I still have this issue since years.
I'm syncing clients against a central WebDAV server, using davfs2+unison on 
Linux (and Foldersync on Android).
When having a weak uplink, sometimes a bunch of files gets detected as 
remotely missing, going to delete locally. In the next sync turn having a 
stable uplink, the files get deleted remotely as expected...
This is dangerous. Who is responsible for that? I guess it's the 
filesystem, is it? A FUSE file system should return something like IO 
errors or just block, but nothing like "file not found" on a weak network.
Having seen that it's highly risky to do my syncs via public (VPN secured) 
networks.

While unison has some user interaction and I don't run it headless I often 
can check before applying this issue. But on hundreds of files I often need 
to check if unison is right about deletions. On Android with Foldersync 
running always completely headless (accepting/deleting latest file version) 
I have never seen this issue and it runs almost always on uncertain mobile 
uplinks.

Best regards,
Mo

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

------=_Part_801171_1520203165.1767955611931
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>Coming from=C2=A0https://github.com/bcpierce00/unison/issues/989 ...</=
div><div><br /></div><div>I still have this issue since years.</div><div>I'=
m syncing clients against a central WebDAV server, using davfs2+unison on L=
inux (and Foldersync on Android).</div><div>When having a weak uplink, some=
times a bunch of files gets detected as remotely missing, going to delete l=
ocally. In the next sync turn having a stable uplink, the files get deleted=
 remotely as expected...</div><div>This is dangerous. Who is responsible fo=
r that? I guess it's the filesystem, is it? A FUSE file system should retur=
n something like IO errors or just block, but nothing like "file not found"=
 on a weak network.</div><div>Having seen that it's highly risky to do my s=
yncs via public (VPN secured) networks.</div><div><br /></div><div>While un=
ison has some user interaction and I don't run it headless I often can chec=
k before applying this issue. But on hundreds of files I often need to chec=
k if unison is right about deletions. On Android with Foldersync running al=
ways completely headless (accepting/deleting latest file version) I have ne=
ver seen this issue and it runs almost always on uncertain mobile uplinks.<=
/div><div><br /></div><div>Best regards,</div><div>Mo</div>

<p></p>

To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">unison-u=
[email protected]</a>.<br />

------=_Part_801171_1520203165.1767955611931--

------=_Part_801170_528114627.1767955611931--