did not pick any blocks. blocking peer temporarily?

[Guest idef1x]

I see this in my sync.log file on my Linux machine and looks like it has to do with a .!sync file not finishing syncing. Any ideas what that log entry means? Blocking sounds like no syncing possible between that particular client, but what's going on and why?

[Guest glombus]

I'm seeing the same thing in my sync.log file.  I have a ~54GB sync that hasn't gone beyond 2.3GB over three weeks.  It seems like it's stuck.

 

The sync is of a home dir on a Windows machine.  It's synching read-only to a backup on a linux machine.

 

On the linux machine I see that error idef1x mentions.  It seems like it's related to a single file repeatedly failing to pass the hash check.  This error repeats constantly.  It seems like no other files for this sync will transfer due to this error.

[20130924 21:16:31.826] Incoming connection from 192.168.1.7:21626[20130924 21:16:41.566] Incoming connection from 192.168.1.7:21626[20130924 21:16:51.606] Incoming connection from 192.168.1.7:21626[20130924 21:17:01.966] Incoming connection from 192.168.1.7:21626[20130924 21:17:11.602] Incoming connection from 192.168.1.7:21626[20130924 21:17:21.895] Incoming connection from 192.168.1.7:21626[20130924 21:17:31.575] Incoming connection from 192.168.1.7:21626[20130924 21:17:41.974] Incoming connection from 192.168.1.7:21626[20130924 21:17:43.706] Extension: ipv4:[xxx.xxx.xxx.xxx] for 'MSIMGSIZ.DAT'[20130924 21:17:45.235] xxx.xxx.xxx.xxx:20599: did not pick any blocks. blocking peer temporarily[20130924 21:17:45.242] *** MSIMGSIZ.DAT: PIECE 0 FAILED HASH CHECK[20130924 21:17:45.617] *** MSIMGSIZ.DAT: PIECE 1 FAILED HASH CHECK[20130924 21:17:46.787] xxx.xxx.xxx.xxx:20599: did not pick any blocks. blocking peer temporarily[20130924 21:17:47.280] *** MSIMGSIZ.DAT: PIECE 0 FAILED HASH CHECK[20130924 21:17:47.700] *** MSIMGSIZ.DAT: PIECE 1 FAILED HASH CHECK[20130924 21:17:47.700] Banned xxx.xxx.xxx.xxx:20599 until forever[20130924 21:17:51.614] Incoming connection from 192.168.1.7:21626[20130924 21:17:53.525] Extension: ipv4:[xxx.xxx.xxx.xxx] for 'MSIMGSIZ.DAT'[20130924 21:17:54.075] xxx.xxx.xxx.xxx:20599: did not pick any blocks. blocking peer temporarily[20130924 21:17:54.103] *** MSIMGSIZ.DAT: PIECE 0 FAILED HASH CHECK[20130924 21:17:54.285] *** MSIMGSIZ.DAT: PIECE 1 FAILED HASH CHECK[20130924 21:17:55.792] xxx.xxx.xxx.xxx:20599: did not pick any blocks. blocking peer temporarily[20130924 21:17:56.160] *** MSIMGSIZ.DAT: PIECE 0 FAILED HASH CHECK[20130924 21:17:56.348] *** MSIMGSIZ.DAT: PIECE 1 FAILED HASH CHECK[20130924 21:17:56.348] Banned xxx.xxx.xxx.xxx:20599 until forever[20130924 21:17:58.349] Extension: ipv4:[xxx.xxx.xxx.xxx] for 'MSIMGSIZ.DAT'[20130924 21:17:58.903] xxx.xxx.xxx.xxx:20599: did not pick any blocks. blocking peer temporarily[20130924 21:17:58.927] *** MSIMGSIZ.DAT: PIECE 0 FAILED HASH CHECK[20130924 21:17:59.128] *** MSIMGSIZ.DAT: PIECE 1 FAILED HASH CHECK

I guess I'll try excluding that file on the source and see if things start working

[Tel]

I have seen a lot of these bans on my logs, usually following a file that was in use so wasn't able to be synced. Wish the SW was clever enough to try x times and then wait for say 10 minutes and then try once every 10 minutes until the file is sucessfully synced.

[bradmurray]

I have this problem all of the time. For example if I modify a bunch of metadata in MP3 files and they have to be re-synced I will get this on a bunch of random ones. The only solution I have found is to stop both clients, manually copy the file, delete the *.SyncPart and *.!sync files in the destination folder, and restart syncing. I usually pause the client on my macbook before I do the batch mods and resume it when I'm done so I don't think it is an issue with it trying to pick open files.