Transmission loses track of downloaded content on external drives when they're unmounted

Bug #676325 reported by Mike Birch on 2010-11-17
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fix Released
transmission (Ubuntu)
Charles Kerr

Bug Description

Binary package hint: transmission

Transmission 1.93 (10621)
Karmic, Lucent and possibly Maverick. Currently using netbook edition but this bug seems to be by design.

Download complete torrents to a removable USB drive.
Close Transmission.
Unmount drive (or wait for the system to forget about it! Grr!)
Start Transmission.
* All of the torrents are unavailable as expected.
End Transmission, re-mount drive and start transmission.
The torrents are all paused _with zero bytes downloaded_.
Starting a torrent results in it transmission blindly attempting to re-download data over the top of what's already there.
Only by explicity verifying local data (a big task with >100 torrents) does it accept that they are already downloaded, not to mention those you manually paused which are now indistinguishable from any other.

Missing files should not zero totals and pause the torrent. For the current session, they should be marked invalid but their general status should be left untouched. If the data file reappears on subsequent sessions, it should continue where it left off. If it insists on verifying the data, it should do so quietly and not explicitly require it. Re-downloading over the top is right out!

Charles Kerr (charlesk) wrote :

This is in progress for 2.20

Mike Birch (mike-immortalsofar) wrote :

Great! Can I add a little addition, still on the theme of dynamic file systems?

If, during a download, the destination device is removed or dropped then the download continues unaware. It can claim to have downloaded the entire file and it is only when the device is remounted and local data verified that the problems come to light.

Reproduction steps:
Start download to a removable device.
Remove device.
(Download continues without successfully saving to the device).
Reconnect device.
Verify local data.
(The percentage downloaded gets reduced until the actual saved data is reached - this part is correct).

Check the return value when writing data. When a write (perhaps with retries) fails, the destination file should be marked temporarily unavailable or, at worst, the torrent paused.

Charles Kerr (charlesk) on 2010-12-22
summary: - Missing data files lose track of what's been downloaded.
+ Transmission loses track of downloaded content on external drives when
+ they're unmounted
phonixor (phonixor) wrote :


On launching transmission, check for any devices that should have torrents on them (but forgotten or whatever the technical term is..) and enable them...
maybe a quick scan to see if the files are there, and then just assume that the last known status of the client was the right one... so continue the download, instead of a full verify local data...
(i think its pretty uncommon to have multiple clients working on the same torrent, so this behavior would be preferred)

same behavior if the device is unplugged and reinserted during a torrent download:
(quick rescan and asume its ok...)

Charles Kerr (charlesk) on 2010-12-27
Changed in transmission (Ubuntu):
status: New → In Progress
assignee: nobody → charles (charles-rebelbase)
importance: Undecided → Medium
Changed in transmission:
status: Unknown → Confirmed
Changed in transmission:
status: Confirmed → Fix Released
phonixor (phonixor) wrote :

Damnit Ubuntu needs to update its repositories!!!
2.13 v 2.22
more then a month behind for there default apps is unacceptable...
(its not a library, so no need to wait 6 months... ... though they waited longer :@)

Charles Kerr (charlesk) wrote :

Thank you for your bug report. To maintain a respectful atmosphere, please follow the code of conduct - . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind.

Sergey Fukanchik (fuxx) wrote :

Can this bug be fixed in 10.04 which is Long Term Support?

Krzysztof Klimonda (kklimonda) wrote :

This bug has been fixed around 2.20 which means it's fixed in 11.10 - quick glance at the upstream bug report shows that it's not suitable for backporting it to the transmission release from 10.04, especially this close to the 12.04 release.

I'm closing the bug as "Fix Released" as it's fixed in the stable Ubuntu release.

Adolfo Jayme (fitojb) on 2012-03-28
Changed in transmission (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.