Transmission download stuck in the default download dir

[THE_KINGDOM]

I have a download from transmission stuck in the default download directory of:
/mnt/RobFreeNAS/jails/transmission_1/usr/pbi/transmission-amd64/etc/transmission/home/Downloads

For the life of me I have tried everything I know to try and get the file in this directory to show as a windows share so I can move it to the correct directory and change this default download directory to an actually accessible directory like /media

Does anybody have a suggestion for how I can get this file out of this directory..

Thank you

 

[SweetAndLow]

http://zfsguru.com/forum/zfsgurusupport/512

This is how you modify transmission directory locations.

 

[THE_KINGDOM]

http://zfsguru.com/forum/zfsgurusupport/512

This is how you modify transmission directory locations.

I'm not trying to modify any directory. I know how to change the transmission download folder/directory. Thank you

I cannot get the file out of the directory I posted (in OP), this is the DEFAULT download directory of the transmission plugin, UNLESS you modify it, which I forgot to when reinstalling the plugin while troubleshooting.

I really need help with how to get this file out, freenas won't allow me to have a "share" connected to this directory. I have a ~5gb file inaccessible in a transmission directory.
Is there a shell command I can use or something? Any way to get this file and move it to "transmission/media", so at least I can attach a windows share to it and have access to this file

 

[SweetAndLow]

You change the download directory to the directory you mounted in the jail from your zfs pool. Then you use your shares to share that directory or dataset.

 

[THE_KINGDOM]

You change the download directory to the directory you mounted in the jail from your zfs pool. Then you use your shares to share that directory or dataset.

I still don't think this addresses the issue..
Just to be clear... are you under the understanding that I've used transmission many times?
I know how to set up the download directory and get it to share to windows. I'm not asking how to use and set up transmission... I know how to do that. Used it since I set up FreeNas.

BUT because I forgot to setup the download directory to /media (during reinstalling the plugin, due to prior issues) it has a default download directory of:
/mnt/RobFreeNAS/jails/transmission_1/usr/pbi/transmission-amd64/etc/transmission/home/Downloads
WHICH I forgot to revise to: /media

And this is the problem I've been having with mounting that directory in the jail:

Can't even set the jail storage "destination" to that folder because the directory is too long.....

BTW this is not the first time this has happened to me, the last time was when I first created a FreeNas and I believe I had to delete the plugin, jail, data-set everything.. just to start over and erase this inaccessible data. There must be a way to get this file out of:
/mnt/RobFreeNAS/jails/transmission_1/usr/pbi/transmission-amd64/etc/transmission/home/Downloads

OBJECTIVE:
- need to move downloaded file out of the above directory to /media or anywhere. Either by a visible share to extract the file out or by using CLI to move it to transmission/media .. don't know how

 

[SweetAndLow]

Make the destination /media/something. Then just use the jail shell and copy the files from that long path to /media/something then those files will be in your normal pool.

This seems pretty straight forward to me. Maybe you are trying to do something else that isn't getting explained well?

 

[THE_KINGDOM]

Make the destination /media/something. Then just use the jail shell and copy the files from that long path to /media/something then those files will be in your normal pool.

This seems pretty straight forward to me. Maybe you are trying to do something else that isn't getting explained well?

That's exactly what I'm trying to do "move" files from that long directory to /media

What command(s) should I use to do so?

 

[SweetAndLow]

mv <source> <destination>

From in the jail run something like this.

Code:

mv /usr/pbi/transmission-amd64/etc/transmission/home/Downloads /media/something/

 

[THE_KINGDOM]

so I've got to the directory in shell CLI, can't move the file. don't know how.. massive long file name.. tried moving.. using mv <file name> </dir>

still no dice..

Sorry to say it but it blows my mind I'm even having to do this.. Why on earth is the default download directory for transmission an inaccessible and un-shareable directory?!?!

okay finally tried to move file using the commands you specified and it says "operation not permitted"

 

[THE_KINGDOM]

finally managed to do it, no idea how.. I believe when it said operation not permitted, somehow it still moved (or I should say copied) the file and created a subdirectory.. anyways.. this is a bug and a massive one at that..

I used a move file command and it copied the file and directory.. I still had to use separate cmd's to remove the original file which deleted the whole directory.

 

[SweetAndLow]

Naw not

finally managed to do it, no idea how.. I believe when it said operation not permitted, somehow it still moved (or I should say copied) the file and created a subdirectory.. anyways.. this is a bug and a massive one at that..

I used a move file command and it copied the file and directory.. I still had to use separate cmd's to remove the original file which deleted the whole directory.

Naw not a bug you just did it wrong. You should take your time and figure out exactly what it is you want to do then ask a good question. The default transmission download directory is correct. There is no reason for the default to be on your specific mount point you created unless you told it to go there. Why didn't you just do that? Transmission even moves all the files for you if you do this.

 

[SweetAndLow]

Naw not

finally managed to do it, no idea how.. I believe when it said operation not permitted, somehow it still moved (or I should say copied) the file and created a subdirectory.. anyways.. this is a bug and a massive one at that..

I used a move file command and it copied the file and directory.. I still had to use separate cmd's to remove the original file which deleted the whole directory.

Naw not a bug you just did it wrong. You should take your time and figure out exactly what it is you want to do then ask a good question. The default transmission download directory is correct. There is no reason for the default to be on your specific mount point you created unless you told it to go there. Why didn't you just do that? Transmission even moves all the files for you if you do this.

 

[THE_KINGDOM]

Naw not

Naw not a bug you just did it wrong. You should take your time and figure out exactly what it is you want to do then ask a good question. The default transmission download directory is correct. There is no reason for the default to be on your specific mount point you created unless you told it to go there. Why didn't you just do that? Transmission even moves all the files for you if you do this.

I don't think you read or understood the first post or any post thereafter.

The DEFAULT download directory of transmission cannot be shared as it EXCEEDS the amount of characters allow in order to mount it in the jail storage for a share. I did nothing wrong in fact.

If you know a way to share that directory then please let us know! WHY did I have to use CLI to force move the files from an inaccessible and un-sharable directory? If I could have attached a direct share.....?????? Do u think I just wanted to make it hard for myself ?! Lolololol...................

 

[SweetAndLow]

You don't share the default download directory, that isn't how it works. You change the download direcotry to be the mounted storage from your pool and you share that directory from your main pool. You should never touch anything in the jail dataset, you should never share a directory in the jails dataset and you should ignore that the jail dataset exists on the filesytem.

Yes you are making it hard for yourself.

 

[THE_KINGDOM]

But if you have already downloaded to that directory prior to chnaging it to /media.. Then what? How do you share the file?

if u read above u cannot share directly that directory it's TOO MANY characters.

Ive taken screen shots......

 

[danb35]

No, it isn't a bug. @SweetAndLow is confused because what you've asked isn't what you actually want to do. No, you can't share the default download directory. That is not the solution to your problem. The solution is two-fold: (1) change the download directory to something you can share, and (2) move the file you already downloaded to somewhere else that is more accessible.

The plugin does not know (and cannot know) how you have the rest of your system set up, what shares you have, and what storage (if any) you're going to mount to the jail that contains the plugin. It therefore cannot set the default download directory to something accessible to the rest of your system, and its failure to do so is therefore not a bug.

If you've failed to set the download directory to something you can share before you download something, any files will be in the default directory. You'll need to use the CLI to move them, and the command is mv <source> <destination>. It really is that simple. Except that it isn't, exactly...

When you use the mv command within the same filesystem, files (or directories) are moved instantly, as it's simply a matter of updating the directory information to reflect that the file is in a new location. All ownership/permissions are automatically preserved. When you use it across filesystems (and datasets and mounted storage are treated as separate filesystems), it's a bit more complicated. The file is copied to the new location, the ownership is changed to match the existing file, the permissions are changed, and the old file is deleted. But if the destination is using ACLs rather than Unix permissions, the change ownership/permissions will fail, and you'll get the message "operation not permitted". The file is still copied, and it's still removed from its source location, but the ownership and permissions probably won't match.

 

[THE_KINGDOM]

No, it isn't a bug. @SweetAndLow is confused because what you've asked isn't what you actually want to do. No, you can't share the default download directory. That is not the solution to your problem. The solution is two-fold: (1) change the download directory to something you can share, and (2) move the file you already downloaded to somewhere else that is more accessible.

The plugin does not know (and cannot know) how you have the rest of your system set up, what shares you have, and what storage (if any) you're going to mount to the jail that contains the plugin. It therefore cannot set the default download directory to something accessible to the rest of your system, and its failure to do so is therefore not a bug.

If you've failed to set the download directory to something you can share before you download something, any files will be in the default directory. You'll need to use the CLI to move them, and the command is mv <source> <destination>. It really is that simple. Except that it isn't, exactly...

When you use the mv command within the same filesystem, files (or directories) are moved instantly, as it's simply a matter of updating the directory information to reflect that the file is in a new location. All ownership/permissions are automatically preserved. When you use it across filesystems (and datasets and mounted storage are treated as separate filesystems), it's a bit more complicated. The file is copied to the new location, the ownership is changed to match the existing file, the permissions are changed, and the old file is deleted. But if the destination is using ACLs rather than Unix permissions, the change ownership/permissions will fail, and you'll get the message "operation not permitted". The file is still copied, and it's still removed from its source location, but the ownership and permissions probably won't match.

Good response I have to say. Thank you.
This is exactly what I've been dealing with.

The reason I think this should be labelled as a bug is because the default download directory shouldn't be a directory which is too long to share, instead it should default for example to /media just for simplicity and compatibility.

What a bunch of hoops you have to jump through just because I didn't change the default download directory " this time"

 

[danb35]

There are a couple of problems with your suggestion. First, you should never share any part of the jail. That leads to messing up ownership and permissions inside the jail, which leads to the jail not working. Second, once you've saved something in /media, you now can't mount storage there--you can only mount a filesystem into an empty directory.

There is no "bunch of hoops you have to jump through"--you just move the downloaded file to where you want it to be.

 

[pirateghost]

This isn't a bug but rather you not understanding the structure of a jail and the storage.

You might want to take some time to learn those things.