I thought I read somewhere that user0 was no longer being created because the new Mover with 6.4 doesn't need it?  If so can it still be created or a directory that has the same properties?  Even if only by the command line?

 

I ask because I use MC to move from user0 to cache all the time.  Then the files (that were on multiple drives originally) get moved from the cache drive back to a single disk share.  The reason I can't just do it with user shares directly is that disks fill up and then that copy would terminate because the directory is only allowed on one disk or files in it end up on multiple disks.  I don't want the copy to just stop because I have the folder limited to a single drive but I also don't want it to end up on multiple drives.  So I copy the files to an empty drive and then consolidate files later.  I'm usually moving multi TBs at a time.  Just got done moving 12+ TB for instance to 2 8TB empties in my array and am currently using user0 to cache and then cache to disk share.  The files that get copied to unRAID are not in any order or grouping just a bunch of files in a directory.  I move them to unRAID to free up space on the original PC then I group the files on unRAID which usually amounts to creating directories with the same names as already exist on other drives in the array and let unRAID present the files in one group.  But then later (now that space is not an issue on the original PC) I copy from user0 to cache to consolidate like I said.

 

Sorry thought some background would help on WHY I want this capability if it is disappearing - and not sure it even is - hence the questions at the top.

Edited July 27, 20178 yr by BobPhoenix

Took it out out originally in -rc1, then others came up with reasons to keep it, so put back in -rc5.  We took it out to simplify things and in future it might be banished again.  What you're doing obviously works but is error prone if not careful.  The rewrite of 'mover' actually permits many kinds of share move operations such as depopulating a disk or rebalancing shares, we just need get around to writing a UI for it...

12 minutes ago, limetech said:

The rewrite of 'mover' actually permits many kinds of share move operations such as depopulating a disk or rebalancing shares, we just need get around to writing a UI for it...

Perhaps a collaboration with https://github.com/jbrodriguez/unbalance#screenshot would be in order.

OK.

 

I thought of a work around that I can do with a user script.

 

Basically:

1. Copy to a different directory on the cache drive. 
2. Move the files on the cache drive to the old directory. 
3. Delete the original directory on array. 
4. Finally move them from cache to array with mover.  Maybe just move from cache to disk share if I don't want mover to do it.

Or variations..

Edited July 28, 20178 yr by BobPhoenix