Many torrents say "Waiting to check existing data"

[cmlawson]

Now that I've upgraded to the new version, MANY of my torrents have this 'Waiting to check exisiting data...' message. See attached.

What can I do to fix this?

Screen shot 2010-03-10 at 7.38.43 AM.png (40.64 KiB) Viewed 6832 times

[livings124]

Wait for them to check the data. Only one torrent will do a hash check at a time.

[cmlawson]

I hear you but it's not doing that. If it takes more than 24 hours and the message still reads as pictured, I'd have to conclude something is wrong. Right?

PS I upgraded to v1.92 to no avail.

[livings124]

Are all of them showing that? There should be one currently checking current data.

[cmlawson]

They're all showing that but you know what I just spotted, it's basically just making it's way through the list hella slow. Really, really, slow. It's used to just speed through there and knock them all out but for some reason the new version are going through it with a fine tooth comb and it's taking days to even get to the new stuff that needs downloaded.

Not sure if that's by design by I can verifiably say the old design used to burn through the list.

[livings124]

The bottleneck is your harddrive. It has always been like this.

[cmlawson]

I've been using this for over a year now and my hard drive is a MyDrobo and since it hasn't happened *before* this last upgrade, I have to politely disagree with you. I'm open to a solution but what you're saying goes against common sense and logic here.

[cmlawson]

Again, nothing "new" on that front. Been using it for years with no issues. The one new thing I did was use the bandwidth limit for certain hours during the day. Then, I found that 50 page thread on it just spinning the machine down. Turned that off and it's working fine now. Kinda sucks because that's a killer feature.

Kinda begs the question though, if that thing DOES cause all these issues, why is it even in there?! I know one of the programmer went on there and got all defensive about how it's a Mac or Quicktime issue or whatever but how about dealing with reality instead? If it causes problems, fix it or leave it about.

Just my 2 cents...

PS Thanks for your help all along.