Hi there,

 

I have the download folder on /mnt/cache. It is still transparently shown in /mnt/user/. I have recently installed the cache drive, so all tools are still pointing to /mnt/cache, even htough I have moved some shares physically to /mnt/cache.

 

When I configure SABnzbd etc., does it make a difference with respect to the other drives in /mnt/drive* staying spun down, if I use /mnt/user instead of /mnt/cache?

 

Thanks for caring,

JC

/mnt/user/

shows all shares, and, any files written here will be dumped to the cache drive if they're meant to go there, or, directly to the array if the cache drive option is disabled. This will also list (for reading) all files on both the cache drive & array.

/mnt/user0/

shows all shares, and, any files written here will be dumped directly to the array, even if the cache drive was the intended destination. This will also only list (for reading) files on the array.

/mnt/cache/

shows only the shares that currently have files on the array, and, any files here will be dumped to the cache drive, and, only the cache drive. It will ignore any settings in the user share settings.

/mnt/disk*/

shows only the shares that currently have files on the selected disk, and, any files here will be dumped directly to this specific disk, I highly recommend you don't use this option unless you have a good reason to.

 

Basically, use /mnt/user/ unless you have an extremely good reason otherwise, and, basically never use /mnt/disk/.

/mnt/user0/

Shows all shares WITHOUT SHOWING any content that may still be on the cache drive (not yet moved to the protected drive.)

 

And... ALWAYS use the /mnt/disk*/shares when YOU want to control where a file is being stored.

/mnt/user0/

Shows all shares WITHOUT SHOWING any content that may still be on the cache drive (not yet moved to the protected drive.)

 

And... ALWAYS use the /mnt/disk*/shares when YOU want to control where a file is being stored.

 

Isn't that what I said? And, controlling where the files are being stored is the reason that I was talking about when I said "shows only the shares that currently have files on the selected disk, and, any files here will be dumped directly to this specific disk, I highly recommend you don't use this option unless you have a good reason to."

Won't anything written to /mnt/cache that is not in a cache-only share or hidden (starts with .) folder be moved to the array?

Won't anything written to /mnt/cache that is not in a cache-only share or hidden (starts with .) folder be moved to the array?

 

Err, yes, although, I'd still recommend writing to /mnt/user as it means that you can change all applications settings just by updating your share settings, vs traversing through all your programs to reverse what you set up.

Guys, thanks for clarification of the different roles of the /mnt/... pathes. This was what I kinda understood from the forum before. However, I am unsure if the array drives will stay spun down if I use /mnt/user in the application and plugin config files. Ow would it be better to use /mnt/cache to be sure only the cache drive is spun up for stuff that uses the cache drive and the other drives will stay spun down.

 

TIA