remapping drive/path

[harryb382003]

I sustained a loss of a few drives and am now in a recovery process.

Is there a way to remap drives from, for example:

bing/bang/boing/foo/bar/baz
to
bing/bang/<MY NEW PATH>/foo/bar/baz

or do I truly have to do in batches, sometimes individually for 1000+ torrents?

[Peter]

Yeah you can remap like that.
But it depends on the platform.

On Windows it's called Junction point:
https://www.computerhope.com/jargon/j/junction.htm

This tool lets you do it easy:
https://schinagl.priv.at/nt/hardlinkshe ... nsion.html

-

On Linux its called "symlink" and "hard link".
https://stackoverflow.com/questions/185 ... -hard-link

-

On Mac, I don't know. I suppose hard links too but this repo is a bit old: https://github.com/selkhateeb/hardlink

[harryb382003]

Sorry. Maybe I could have worded that better.

I know how to do symlinks and what not, but what I meant was to remap the download directory(s) of torrent(s).
There was some other client that I once upon a time used where I could just edit a single element of a path and not have to worry about the subdirectories that came after it. If I try that in QBittorrent, those sub paths become lost.

The original drives exist but are failing, so I am recovering the data to new drives which qBittorrent needs to know about.

[bob2306]

Why don't you just copy the content to the new drives and then change the mount points.

[bob2306]

On Linux its called "symlink" and "hard link".
https://stackoverflow.com/questions/185 ... -hard-link

On Mac, I don't know. I suppose hard links too but this repo is a bit old: https://github.com/selkhateeb/hardlink

For this application you would need to link directories.

By design, hard links can't link directories in any UNIX derived OS. Using that Mac tool is not a good idea unless there's a compelling need for it, and you thoroughly understand the issues. Also hard links can't span separate filesystems anyway.

[harryb382003]

My issue is until such time that I can get all my data off the drive(s), the drive(s) is/are effectively 'locked'. Meaning I cannot change the drive name so the the new drive can have it.
Additionally, I am trying to recover the dying data from rather large drives (5 & 8 TB) into the freespace of other drives.

I just want to be able to tell qBittorrent the new location (set path), en masse, without losing sub paths.
Currently it appears that this is not possible.

However I have noticed certain improvements in this regard. Maybe they were always there but I am only just now noticing.

Either way. I will add this the the recovery script I am working on.

[bob2306]

My issue is until such time that I can get all my data off the drive(s), the drive(s) is/are effectively 'locked'. Meaning I cannot change the drive name so the the new drive can have it.

FWIW you never actually mentioned what the OS is.

[harryb382003]

MacOS but it doesn't really matter as I have zero intention or interest of resolving this at the OS level.
It's not something requiring OS level resolution.

It is merely a minor application issue I am trying to work through.
To be clear, I am not suggesting that there is anything wrong with qbittorrent. It was just something that I could do with another client I once used so I thought I would ask about the one that I now use.

I have been spending the last many months working on a recovery script in perl. I well merely add this to my ToDo list.