Ticket #1032 (assigned feature-request)

Opened 4 years ago

Last modified 3 months ago

Error-out if downloaded torrent data is suddenly missing

Reported by: s0undt3ch Owned by: s0undt3ch
Priority: major Milestone: 1.4.0
Component: core Version: master (git branch)
Keywords: Cc: non7top@…, luther138@…

Description

When a seeding torrent data is moved on the file-system from outside deluge, deluge starts thinking it's a new torrent and starts downloading it again(at least within server restarts). The correct behaviour would be to error the torrent giving it a meaningful status message like "Downloaded torrent data not found" or something like this, and if the user actually wants to re-download the torrent, have him resume it.

Change History

  Changed 4 years ago by andar

  • version 1.1.9 deleted
  • milestone changed from 1.2.0 to 1.3.0

  Changed 3 years ago by damoxc

  • milestone changed from 1.3.0 to 1.4.0

  Changed 2 years ago by Cas

  • type changed from bug to feature-request

Changed to feature request as it is not a bug per-se

  Changed 2 years ago by Cas

  • summary changed from Force error when torrent data is moved from outside deluge to Error-out if downloaded torrent data is suddenly missing

  Changed 2 years ago by s0undt3ch

  • status changed from new to assigned
  • owner changed from andar to s0undt3ch
  • version set to git master

A fix is being cooked...

  Changed 18 months ago by non7top

  • cc non7top@… added

  Changed 3 months ago by SisyphusMyth

That would be a great "fix". If you need help implementing it, please contact me.

  Changed 3 months ago by luther138

  • cc luther138@… added
  • type changed from feature-request to bug
  • milestone changed from 1.4.0 to 1.3.x

Is this still being looked into? Rebooting a machine that has a failed mount point, will cause all of the seeding torrents to redownload to a new location. This can be very damaging to a user without an unlimited data plan (as well as damaging to a users ratio on private trackers).

While this isn't the exact case this bug describes I believe that a solution to one would be a solution to the other.

I would consider this more of a bug then a feature-request, torrents shouldn't start downloading to a new location without a warning or user interaction.

SisyphusMyth?: Since nobody has looked at this in 15 months I am

sure they would be glad to have your help.

Thanks.

follow-up: ↓ 11   Changed 3 months ago by Cas

  • type changed from bug to feature-request
  • milestone changed from 1.3.x to 1.4.0

Please do not change ticket settings.

in reply to: ↑ 10   Changed 3 months ago by luther138

Replying to Cas:

Please do not change ticket settings.

My sincere apologies.

I am assuming from your terse retort that you don't agree.

A seeding torrent redownloading to a new location could incur charges to a user who's ISP has a usage-based pricing plan. Costing users extra money seemed like a bug.

Thanks for your attention to this, I look forward to having it as a feature in 1.4.0

-Luther

Note: See TracTickets for help on using tickets.