I was a bit surprised to see that folders created on the cache drive appear as user shares, even though the cache drive is not part of the protected array. I use the cache drive currently without it being allocated to any user shares. This is because the mover script only handles folder exceptions that start with ".". Those folders are not visible on OS X and make it unpractical to use and invisible to many standard apps. Each root folder I create on the cache drive creates a user share.

 

I guess that this is not really a problem as such, since the parity drive is not used for the cache drive, but I would prefer if it would be possible to have a folder exclusion list, that would make the mover script more flexible and keep the excluded folders from showing up as user shares.

 

Roland

I haven't tested this, but I would think that those folders are going to get copied over to your array anyways.  It's the whole purpose of the cache drive.  Feel free to test it out.  Just create a completely new folder, put a file inside it, then run the mover script manually.  Now check all of the drives in your array.  Does that new folder show up on one of them?

My cache drive is not assigned to any user shares for this reason. There are folders that I don't want to have copied to the array, but the mover script is indiscriminate when it comes to folders unless they start with a ".". Since the cache drive is not assigned to any user shares, running the mover script should have no affect. If it does then this is incorrect behavior.

 

What I have noticed is that the user script checks for the user0 directory.

 

if [ ! -d /mnt/user0 ]; then

  exit 0

fi

 

If you test assigning the cache to a user share it seems the user0 directory is created. Removing the assignment does not remove the user0 directory. The mover script then runs no matter if the cache is assigned or not. Directory exceptions are not really possible unless you are a regex expert as the mover script now works.

If you aren't using the Cache drive with your User Shares, could you add something like the following to your go script?

echo ; >path_to_mover/mover

 

If you aren't using the Cache drive with your User Shares, could you add something like the following to your go script?

echo ; >path_to_mover/mover

 

 

Sure I can add it. Should I write exactly "echo ; >path_to_mover/mover" or "echo ; >usr/local/sbin/mover".

 

 

Sorry, I was in a big hurry to get out the door, and didn't take time to look up the path, or explain it.

 

The command should be:

echo ; >/usr/local/sbin/mover

 

You probably already understand it, but for others, this just replaces the mover script with a dummy one, that does nothing at all.  It's a simple hack, and there's probably a better way to do it, by disabling the call to the mover script, perhaps editing the cron stuff?  I can't confirm, I don't use a Cache drive yet.

 

For now I changed the minimum free space variable to some huge number (20000000000000) to avoid having the script run. Thanks for your suggestion on replacing the mover script. I am hoping the the cache and mover function will be refined in the future so that it will be easier to combine with user shares and other applications.