Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[xpmps]

After this change is now a problem. Really fixed a bug?
Before, when you walked in you could see the folder volume_1 P2P and manage from there. Now, after that change can not.
After this arrangement leaves a problem is this. To see if we understand.

To move large files before no problems.
fell within volume_1 \ p2p \ complete and then return back to the folder where you would cut and paste the files, it was super fast. I understand that the information is changed only within the disk directory.
Now, it does not appear in the folder volumen_1 p2p you have to cut and paste into the directory volume_1 going again so that the copying of this information is very slow. because it makes nas source directory ---> PC --- nas target directory.

Go disappointment!

No solution?

I explained?

[ionutm]

I've just copied one file from P2P\complete to some other directory under Volume_1, via the web server over internet, and it's not copying via the remote computer.
It appears however to copy the file, as if I would copy the file to a different disk/volume - and I have a single volume/disk in the nas.

[xpmps]

I do not understand.
I wanted to avoid it from the web interface

[JavaLawyer]

If I understand you correctly, you are referring to the fact that theP2P directory and Volume_1 behave as two separate logical volumes on the DNS-320. When files are transferred between P2P and Volume_1, the files are copied (through the local PC) rather than just moved.

Unfortunately, the P2P directory is intentionally treated as a separate Volume from Volume_1 and there is no easy workaround (that I know of) to circumvent this fact.