Sync to pogoplug drive freezes

Posts: 3 · ken-g-r 28 Oct 2012, 22:09

I have 3 Win 7x64 systems and all have the same problem. Each computer can sync to and from each other over my wireless network and all can sync FROM the pogoplug drive to their respective local drives, but any attempt to sync from a local drive TO the pogoplug drive freezes after 5 seconds. Sync'ing to the pogoplug drive with other programs (synctoy) works OK.
Any ideas?
Thanks

Posts: 7279 · Zenju 29 Oct 2012, 12:25

What version are you using? You could run Process Monitor
https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx
for your test case and send the log file here. Then we should at least see where the program hangs.

Posts: 3 · ken-g-r 29 Oct 2012, 21:30

Thanks for responding. Since my last post, just to be sure I have un-installed, cleaned system and re-installed. Still no change. Using V 5.8 as the attached screen capture shows.NOPE can only attach 1 file So:
V 5.8 Build Oct.1,2012 Unicode x64.
The process Monitor file is just for FFS and is in CSV format. I don't see any difference, hope you do.

Info from the progress screen when the program froze was:
Items remaining 5 (156 MB) fyi there were only 4 files to sync.
Speed 869 KB/Sec
Time remaining 3 Min
Time elapsed 00.04

Other info:
The target folder, which was empty, has 2 files written to it:
- sync.ffs_lock
- MVI_0032.MOV.ffs_tmp
Windows explorer is unusable after the aborted sync process requiring a re-boot of the system.
I did not make any changes to the program as installed.

Thanks again

Posts: 7279 · Zenju 30 Oct 2012, 15:30

>The process Monitor file is just for FFS and is in CSV for

The csv file doesn't seem to contain any useful data. Can you save it in Process Monitor's native format, PML? Start capturing right before you copy to the NAS, so that the log file doesn't become too large.

>Windows explorer is unusable after the aborted

This sounds like the network drive in general is not reachable, which implies this is not a FFS issue. You could try to restart explorer instead of rebooting. Explorer will then presumably work until you access the NAS again.

Posts: 3 · ken-g-r 30 Oct 2012, 20:53

As I mentioned above, FFS does write a couple of files, the lock file and part of the first actual file, before it stops so it FFS is at least accessing the NAS for a few seconds.
As for Process Monitor, will do, in the next couple of days, but first a couple of quick questions:
Should I filter Process Monitor or just capture everything?
I haven't worked with PM before but it looks like it is collecting a lot of data. After collecting 12+ hours of data are you sure the file won't be too big to send?
Thanks

Posts: 7279 · Zenju 31 Oct 2012, 11:37

Maybe before we start looking at the .pml files (which will only reveal the last operation before the system hangs, not the reason) you could further describe the symptoms, and how you think this is related to FFS, and not some general network problem?

Posts: 1 · peterhartmann 6 Nov 2012, 11:20

What version are you using? You could run Process Monitor
https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx
for your test case and send the log file here. Then we should at least see where the program hangs.Zenju

Hi! Sorry for being a bit off-topic, but can you post information on how to obtain this sort of data on Linux? I experience freezing on various files while trying to do a synchronization between mounted LVM snapshot and LVM volume (both JFS). If you tell me how to get relevant debug information, I'll post a nice detailed report.

Posts: 7279 · Zenju 6 Nov 2012, 14:02

Hi! Sorry for being a bit off-topic, but can you post information on how to obtain this sort of data on Linux? I experience freezing on various files while trying to do a synchronization between mounted LVM snapshot and LVM volume (both JFS). If you tell me how to get relevant debug information, I'll post a nice detailed report.peterhartmann

I don't know of a similar tool for Linux. Hower file copying is implemented in terms of fopen, fread, fwrite calls, which will then redirect to the next deeper level of implementation unknown to FFS. If there is some tool available that logs more detailed info about these calls, it might reveal why they are stalling.

Posts: 7279 · Zenju 13 Nov 2012, 16:35

I don't know of a similar tool for Linux. Hower file copying is implemented in terms of fopen, fread, fwrite calls, which will then redirect to the next deeper level of implementation unknown to FFS. If there is some tool available that logs more detailed info about these calls, it might reveal why they are stalling.Zenju

It looks like *ltrace* and *strace* are the pendants for Linux.