Opened 11 years ago

Closed 7 years ago

#3541 closed Bug (incomplete)

cannot move/locate torrent via softlink

Reported by: reardon Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.04
Severity: Normal Keywords:


(on Linux/Debian?)

using transmission-remote --find or --move, you cannot set the torrent location to anything containing a softlink. Only "real" mounts are allowed. Also, transmission-remote (via the daemon) is incorrectly responding with "success" when in fact the relocation failed.

To reproduce, create a softlink to the directory containing an existing torrent.

ln -s torrent_olddir new_torrentlink


transmission-remote -t ## --find new_torrentdir

note that I am properly using the fully qualified name for new_torrentdir.

Change History (2)

comment:1 Changed 11 years ago by reardon

I should add that this behavior holds for bind mounts as well. Only the original mount can be used for a --move or --find. Note as well that there is no problem when adding the torrent, only when moving it.

comment:2 Changed 7 years ago by mike.dld

  • Resolution set to incomplete
  • Status changed from new to closed

It was like that in 2.0x (and before), it is like that now: if both source and destination are the same directory, physical data move is skipped, but torrent location is still updated and success is reported. Unless I'm missing something, what is the issue here?

Note: See TracTickets for help on using tickets.