Moved data file to...now Permission denied

[Bob Loblaw]

So here is my situation. I had all my torrents download to my Macintosh HD drive for a while and I decided that I wanted to move them to an external drive. So, I selected one file and clicked on the "move data file to" option, and the data file moved flawlessly and the seeding of the file continued. I tried one more, of the 150+ torrents i am seeding, and it also worked fine (it moved the whole file folder over to the external drive and continued seeding.) After making sure it worked with these two files I selected all the remaining files, and clicked the "move data to" option and then went to bed, knowing this process would take some time. When I woke up I found that all the data had been moved to my external, but my external had become unmounted and transmission was showing all sorts of errors. Flipped the drive off/on so it would mount and then I checked the external and found that all the data was there. Tested a new torrent download and it properly downloads to the external and then seeds from there fine. However, all my old stuff that I was seeding either ignores the existing data, and tries downloading the entire torrent again, or it is giving me a "Error: Permission denied (/Volumes/1TB Xtra Storage/Torrent Downloads/*********/***********720p.rar). I have transmission set up to trash the original torrent file once the main torrent starts to download, so I downloaded one of the original torrents again to see if it would force a "check for existing data" but it just started downloading the torrent as if there was no data there, even though there was. I had over 400 gb of stuff that I was seeding and I don't want to have to redownload it all. I don't know how to force transmission to check the existing data or get around the permissions issue. Any help is much appreciated.

[Rolcol]

Select the torrents you're having a problem with and [Transfers > Verify Local Data]. Version 2.20 of Transmission will make this process much better by not requiring a verification unless something is found to be wrong during seeding.

[Bob Loblaw]

Select the torrents you're having a problem with and [Transfers > Verify Local Data]. Version 2.20 of Transmission will make this process much better by not requiring a verification unless something is found to be wrong during seeding.

Just tried that and got the message "Can't find local data. Try "Move Data File To…" to find it, or restart the torrent to re-download."

[_5ocks_]

I have too experienced this problem and it is quite annoying. I understand that it is expected behavior-if Tm cannot find ~/Drive it makes that directory-but could something as simple as a checkbox for "don't recreate download directory without user prompt" or something; because after this whole mess starts- plugging the drive back in results in a ~/Drive 1 being shown for the external and then it still tries to download locally to the automatically created directory. Annoying when you are downloading anything large and have slow internets, devastating when you only have 1gb free locally. Maybe there is a better way to handle this all together?

[Jordan]

_5ocks_, that was a problem in earlier versions, but if Transmission 2.20 can't find the data that was there before, it won't even let the torrent be started. That should prevent the ~/Drive folder from being created.

Now, an earlier version of Transmission might have created the ~/Drive folder and then 2.20 is seeing that folder... but if 2.20 is the one wrongly creating the ~/Drive folder, please let us know; whether or not it's reproducible; and if so, what specific steps we should take to recreate the bug in 2.20.

Thanks!