Possible bug with network folder sync
- Posts: 1
- Joined: 20 Jul 2012
I've noticed an odd behavior with FFS. If I'm syncing a network drive (a local network with a \\drivename\foldername path) to a local drive, and the connection to the network is interrupted, FFS says that the sync is complete. Furthermore, in "update" mode, after the connection is restored, it continues to think there are no more files to sync. Only by going to File -> new and setting it up again will it resume. I don't think this is expected behavior, is it? Anyway, I thought I would mention it. Thanks.
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
> connection to the network is interrupted, FFS says that the sync is complete.
I assume FFS was creating new files on the target, when the interruption occurred? When it detects that the source files are not existing anymore, then it assumes the files have been deleted in the meantime and there's nothing left to copy. This handling will be improved in a future version.
> after the connection is restored, it continues to think there are no more files to sync.
When files have changed externally it's sufficient to re-compare to get FFS up to date.
I assume FFS was creating new files on the target, when the interruption occurred? When it detects that the source files are not existing anymore, then it assumes the files have been deleted in the meantime and there's nothing left to copy. This handling will be improved in a future version.
> after the connection is restored, it continues to think there are no more files to sync.
When files have changed externally it's sufficient to re-compare to get FFS up to date.
