Ticket #1232 (closed defect: worksforme)
Session files for torrents containing their own directories appear to be different between 0.7.x and 0.8.x
| Reported by: | jdgbolt@gmail.com | Owned by: | rakshasa |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | rtorrent | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
I came across when I was upgrading from rtorrent 0.7.9 and libtorrent 0.11.9 to rtorrent 0.8.0 and libtorrent 0.12.0 a peculiar problem. When I started up rtorrent again, for some reason some torrents that had been seeding and that had been within their own directory with multiple files within this directory, it came up with a torrent registered as completed but hash check indicated missing pieces type of message, which commonly happens say if you delete files or whatever. For some reason when I performed a hash check, it tried recreating the files within the root download directory tree, and not checking the files within the directory like it has been doing all this time. I've been working with it, trying the subversion version as well, and it would appear that perhaps within the session information for 0.8.x, it stores the directory information as well inside of the session track, since when I went back to 0.7.x after testing it, with a torrent I had tried with 0.8.x to see if the functionality was fully broken, which it didn't appear to be. I went and checked the info page and saw that the directory tree was inserted twice, so rather than ./downloads/foo it said ./downloads/foo/foo. This makes me think that perhaps 0.7.x didn't save that information within the session information, so when it went and checked for the directories in 0.8.x, it said ./downloads/ only, not ./downloads/foo. So when it tried to do a hash check, it could not find the files. This would seem to be the case, since when I went back to 0.7.x everything was back to normal, but the file that I had been downloading for 0.8.x obviously did not work. Not entirely too sure how the logic on this goes, but thought I should notify you of my weird experience. I have also tried the svn version just to ensure that it wasn't already fixed, it wasn't, so this is the only thing I could think of based off of my experiences. Not sure if this is normal behavior or not. Anyway, thanks.
