Losing Data Upon Application Restart!!

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
ksnow42
Posts: 5
Joined: Thu Apr 09, 2009 10:08 pm

Losing Data Upon Application Restart!!

Post by ksnow42 »

every time i restart Transmission, it has to verify all the data... when it verifies it, it looses high %'s (sometimes even gigabytes of data)
can i turn off automatic verifying, or fix this problem in my settings or something?
im on a laptop so im always shutting down and moving.... i would really hate to have to keep transmission up 100% of the time, in order to protect my data..

im on a MacBook, OS X 10.5.6, Transmission 1.5.1
i also used a nightly for a while (dont know which build)... and then switched back to the stable.

any help would be appreciated
ksnow42
Posts: 5
Joined: Thu Apr 09, 2009 10:08 pm

Re: Losing Data Upon Application Restart!!

Post by ksnow42 »

another thing ive noticed is transmission resets my ratio for all my seeds....im not sure if these could be related?
essiw
Posts: 567
Joined: Sat Aug 23, 2008 10:40 am
Location: the Netherlands

Re: Losing Data Upon Application Restart!!

Post by essiw »

ksnow42 wrote:another thing ive noticed is transmission resets my ratio for all my seeds....im not sure if these could be related?
Yes I think those two are related.
Your problem is not that Tranmission is verifing the data but that it doesn't quit "normal" and doesn't save the little things like ratio and not saved data.
If Transmission wouldn't auto verify the data you would start from the beginning (so you still had to verify the data if you wanted to continue)
Are you quiting Transmission on the correct way? (clicking quit then waiting a minut until it is closed) And not forcing it to quit? (or without quiting Transmission to turn the computer of with the button on your computer)
ksnow42
Posts: 5
Joined: Thu Apr 09, 2009 10:08 pm

Re: Losing Data Upon Application Restart!!

Post by ksnow42 »

i was quitting everything normally... i fixed the problem thou by downgrading to 1.42
Post Reply