OK so the 'issue' is with RealtimeSync (the FreeFileSync retries was a bit of a red herring)
i.e. the update that should have been kicked off every 60 seconds (plus mirror time) did not start for >2 hours when copying ~15 GB, so this means that RealtimeSync did not start FreeFileSync until all ...
Search found 11 matches
- 17 Oct 2014, 18:27
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
- 15 Oct 2014, 18:12
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
Re: RealtimeSync Mirror File Update Issue
Please let me know if this is just how it's going to be (e.g. FreeFileSync and RealtimeSync were never designed or intended to be used how I'm trying to use them) so I can decide to try other options, live with it or wait for a fix of some kind?
- 14 Oct 2014, 17:46
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
Re: RealtimeSync Mirror File Update Issue
I can confirm that the data was only mirrored after the entire copy procedure finished (RealtimeSync stayed at ~15% processor usage during the entire transfer).
- 14 Oct 2014, 14:00
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
Re: RealtimeSync Mirror File Update Issue
Also, when copying 876 files in 11 folders with a total size of 14.4 GB from a Windows machine to the Master disk on Lubuntu what I've found is that the mirror doesn't appear to work.
RealtimeSync minimum idle time is 60 seconds, FreeFileSync error retry is 5 times with a delay of 2 seconds.
I ...
RealtimeSync minimum idle time is 60 seconds, FreeFileSync error retry is 5 times with a delay of 2 seconds.
I ...
- 13 Oct 2014, 17:19
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
Re: RealtimeSync Mirror File Update Issue
What it 'looks' like is happening is; when a file system change occurs the file name is recorded, after the minimum time elapses, info for this now missing file is requested, this causes an error, but if retry is pressed the new file name is used?
I know this is probably not what actually happens ...
I know this is probably not what actually happens ...
- 13 Oct 2014, 17:10
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
Re: RealtimeSync Mirror File Update Issue
I've tried 10 seconds and 60 seconds. Both minimum idle times exhibit the problem.
(the 1 second delay I mentioned is for retrying after an error)
(the 1 second delay I mentioned is for retrying after an error)
- 13 Oct 2014, 16:14
- Forum: Help
- Topic: RealtimeSync Mirror File Update Issue
- Replies: 8
- Views: 1094
RealtimeSync Mirror File Update Issue
I'm using Lubuntu and FreeFileSync to mirror two external NTFS USB drives with the master shared via Samba to other networked Windows machines (strange kind of software RAID, I won't go into reasoning for this approach but it does make some sense, honest).
Anyway, with RealtimeSync monitoring ...
Anyway, with RealtimeSync monitoring ...
- 13 Oct 2014, 12:24
- Forum: Help
- Topic: Error Code 28: No space left on device (inotify_add_watch)
- Replies: 5
- Views: 8634
Re: Error Code 28: No space left on device (inotify_add_watch)
Sorry, didn't see that one coming, it's painful having to be asked to Google (i.e. I should have done this already).
Common problem, temporary solution, increase the watches limit (to, say, 512K):
sudo sysctl fs.inotify.max_user_watches = 524288
(worked for me, but I'll probably go permanent and ...
Common problem, temporary solution, increase the watches limit (to, say, 512K):
sudo sysctl fs.inotify.max_user_watches = 524288
(worked for me, but I'll probably go permanent and ...
- 13 Oct 2014, 11:21
- Forum: Help
- Topic: Error Code 28: No space left on device (inotify_add_watch)
- Replies: 5
- Views: 8634
Re: Error Code 28: No space left on device (inotify_add_watch)
Thanks for the update Zenju. Any suggestions regarding where to start looking?
- 13 Oct 2014, 10:56
- Forum: Help
- Topic: Error Code 28: No space left on device (inotify_add_watch)
- Replies: 5
- Views: 8634
Re: Error Code 28: No space left on device (inotify_add_watch)
Quick update;
The issue doesn't appear to be file/folder count, maybe total data size allowed for paths (again a complete stab in the dark).
I've got monitoring to work by removing folders until the error goes away but this is a lower file/folder count than one of the other syncs (I would prefer ...
The issue doesn't appear to be file/folder count, maybe total data size allowed for paths (again a complete stab in the dark).
I've got monitoring to work by removing folders until the error goes away but this is a lower file/folder count than one of the other syncs (I would prefer ...
- 13 Oct 2014, 10:26
- Forum: Help
- Topic: Error Code 28: No space left on device (inotify_add_watch)
- Replies: 5
- Views: 8634
Error Code 28: No space left on device (inotify_add_watch)
I hope this is the correct place to raise this issue. I've done a quick search on the problem but I couldn't find anything obviously relevant.
Situation is; I'm using Lubuntu to sync (mirror) two external NTFS 250GB USB drives using RealtimeSync.
The drives are ~80% full and I've split the task ...
Situation is; I'm using Lubuntu to sync (mirror) two external NTFS 250GB USB drives using RealtimeSync.
The drives are ~80% full and I've split the task ...