I've always encountered the odd huge torrent where checking existing data only gets so far then gives up and the torrent has to be paused and restarted.
However this now appears to happen for all torrents. They get to 100.00% but don't finish, Transmission just keeps my hard-drive thrashing away but never actually does anything until I pause the torrent, then restart it, at which point it appears blue.
So it seems there's something up with checking existing data that is causing it to hang for all torrents now, but I'm afraid I can't give any more details that may help.
I'm running Snow Leopard if that makes any difference.
Checking existing data almost never finishes?
-
Tiny Clanger
- Posts: 3
- Joined: Sun Jun 29, 2008 11:48 am
Re: Checking existing data almost never finishes?
I'm having something similar. Transmission 1.73* crashed, and when I restarted, the torrent was at 37.0Gb of 56Gb, but the check was INCREDIBLY slow, and seemed to freeze at around 42% after a couple of hours. Worse, when I added a second torrent, it stayed at status "waiting to check files", even though it was a new torrent and Transmission had already displayed "0b of 250Mb"!
Surely new torrents shouldn't wait to check files — there aren't any, Transmission has already noted this when it displayed that the transfer was at 0 bytes, so the transfer should just start? (Come to that, why is Transmission not capable of checking more than one torrent at a time? Seems a strange limitation — perhaps it should pause checking large transfers in order to check smaller transfers first, then go back to the large ones?)
I worked around this by pausing all torrents, restarting the new one, then restarting the part-transferred one — but that made the check go down from 42% to 34%! And the number is not increasing! How can restarting the program cause less data to have been checked?
Turning Debug on in the Message Log window doesn't show anything useful: the only message is "Verifying torrent", and it doesn't actually seem to be doing anything after printing that message. Could we at least have some debug messages indicating what's going on with the verification?
I'm not running Snow Leopard — I'm on 10.5.8, so this doesn't seem to be Snow Leopard-related.
If the check is going to be so unreliable, is there any way of skipping it, taking the risk of getting a couple of corrupt files (which can be retransferred later) and just getting on with the download? It's bad enough that it's taken over a week to get this much with my lousy connection, without having to wait another week for Transmission to work out how to verify the torrent!
* 1.74 and 1.75 seemed to be ignoring the bandwidth limits and making my connection unusable. I tried upgrading to 1.76, and the restart has now caused the amount of data checked to go down YET AGAIN. And it STILL is not increasing: even after leaving !
Surely new torrents shouldn't wait to check files — there aren't any, Transmission has already noted this when it displayed that the transfer was at 0 bytes, so the transfer should just start? (Come to that, why is Transmission not capable of checking more than one torrent at a time? Seems a strange limitation — perhaps it should pause checking large transfers in order to check smaller transfers first, then go back to the large ones?)
I worked around this by pausing all torrents, restarting the new one, then restarting the part-transferred one — but that made the check go down from 42% to 34%! And the number is not increasing! How can restarting the program cause less data to have been checked?
Turning Debug on in the Message Log window doesn't show anything useful: the only message is "Verifying torrent", and it doesn't actually seem to be doing anything after printing that message. Could we at least have some debug messages indicating what's going on with the verification?
I'm not running Snow Leopard — I'm on 10.5.8, so this doesn't seem to be Snow Leopard-related.
If the check is going to be so unreliable, is there any way of skipping it, taking the risk of getting a couple of corrupt files (which can be retransferred later) and just getting on with the download? It's bad enough that it's taken over a week to get this much with my lousy connection, without having to wait another week for Transmission to work out how to verify the torrent!
* 1.74 and 1.75 seemed to be ignoring the bandwidth limits and making my connection unusable. I tried upgrading to 1.76, and the restart has now caused the amount of data checked to go down YET AGAIN. And it STILL is not increasing: even after leaving !