hi all

 

quick question, i have a folder in my  user shares called downloads, its actually hosted on disk 5 of my array and set to fill up, no cache drive used.

 

my movies user folder is set to user disk 1,2,3,4 and most free, when i move a folder/file from the downloads folder to my movies folder, it doesnt actually move it to the movies share, it creates a folder called movies on disk 5 and includes this in the movies user share. i have confirmed this by browsing the disk folders in dolphin.

 

i got around this before by ticking exclude all my disks when creating a share. i was told not to do this and the lifering system check advises not to do this either, but if i dont, my shares seem to write to where they want to and not sticking to the rules of only using the disks i set in the share.

 

hope this makes sense the way i have explained it

forgot to mention, i do not use the cache disk for anything apart from VM and docker so there is no mover tasks being completed.

 

Manually move the Movies folder from disk5 then restart the array so the user shares will get reset. If there is already a Movies folder on the disk, it is going to do a move within the disk.

hi thanks for that, but the point i was making is

 

movies = disk 1 2 3 4 only and not anything else.

 

downloads = disk 5 only

 

moving folders from the user share download to user share movies creates a folder on disk 5 called movies?

 

why is this happening? its like the exclude disks if not selected over rules the selected disks. if i exclude the disks, it does as it should and fill up disks 1-4

 

...

moving folders from the user share download to user share movies creates a folder on disk 5 called movies?

...

How the Movies folder was originally created on disk5 is unknown, at least to me. I was only trying to suggest something to try to get it fixed. If the Movies folder no longer exists on disk5 then possibly the move will not include disk5 as a possible destination.

ok ive just created a test folder in unraid and told it on disk 1 only called test, i then moved a file from a folder on disk 12 to the usershare test and it has done the same thing. so it seems that unless i tell unraid to exclude disks, it writes where it wants to ( on both occasions on the same drive that the original file is located)

 

i keep my data seperated on the actual disks so its not a huge pool of space that anything sits anywhere, maybe i shouldnt do this but its more of a failsafe as i have a pnt list every week reporting the contents of each disk so if i lose the parity drive and another disk, i know whats on it to replace from my backups.

 

should i move files and folders only on a disk to disk level and not user level to avoid these problems as i think this will help

 

I am going to load krusader to see if this is a dolphin issue or not as this is how i move stuff around.

Kinda a bug, but probably not really.

 

If you create 2 shares: test and test2 and limit each to different disks, then moving files over the network from one to the other will indeed place them on the correct disks, because each of the smb shares (test & test2) wind up being a different mount point.

 

But, if you do the same thing via a command prompt

 

mv /mnt/user/test/file /mnt/user/test2/file

then the system will not apparently honor the include / exclude settings.  This is basically because at the command prompt, the mount point is /mnt/user, and linux is smart enough to merely rename the file to the appropriate new directory.

 

I think in the real world, this would only affect things inside apps if you are passing /mnt/user mapped to /mnt/user.  On a proper setup with say /downloads mapped to /mnt/user/downloads and /movies mapped to /mnt/user/movies the files will wind up on the correct placement because docker will traverse mountpoints and move instead of renaming.