[[6.5.1] Share with Cache Prefer - Mover Fails [RESOLVED]]

Sure, tack them onto the end. It's just a mission statement.

[[6.5.1] Share with Cache Prefer - Mover Fails [RESOLVED]]

Quote

Specify whether new files and directories written on the share can be written onto the Cache disk/pool if present.

No prohibits new files and subdirectories from being written onto the Cache disk/pool.

Yes indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the Cache disk/pool and onto the array.

Only indicates that all new files and subdirectories must be writen to the Cache disk/pool. If there is insufficient free space on the Cache disk/pool, createoperations will fail with out of space status.

Prefer indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the array and onto Cache disk/pool.

I had to read that a few times to spot the difference! Seems like it could be written a little more succinctly to state that

 

Yes - Write to cache for new, move to array when mover runs. 

Prefer - Write to cache for new, move to cache when mover runs. 

 

Thanks for the pointer. 

[[6.5.1] Share with Cache Prefer - Mover Fails [RESOLVED]]

I did not delete it. 

 

I am using a prefer cache on TV because Plex is recording TV shows there and I want them moved to disk afterwards. 

 

The TV folder exists in cache but not disk#

 

Thanks.

[[6.5.1-rc5] Unable to add docker from existing template.]

1 minute ago, dlandon said:

After some additional testing, the issue of re-installing a template and adding a new docker from CA occurs when there are no dockers installed.  When at least one docker is installed, both operations work properly.

I do not have any dockers installed. I had deleted my docker.img file to reset. 

[[6.5.1-rc5] Unable to add docker from existing template.]

Just now, trurl said:

None of the plugins or dockers are supported by Lime-Tech. If all you want is a basic NAS then go ahead and get rid of all the community stuff.

Lime-Tech provides docker support in the application which is why I selected them and paid for my license. Installing a docker seems to be a core feature and Lime-Tech's own templates, PlexMediaServer and Sync do not work either. 

 

Can we get to the point where we are working on a fix? What else can be provided as information? 

[[6.5.1-rc5] Unable to add docker from existing template.]

8 hours ago, Squid said:

Nothing particularly jumps out in the syslog.  But, word to the wise.  You're better off installing Community Applications (https://lime-technology.com/forums/topic/38582-plug-in-community-applications/) and installing the apps via it.  The repository system has always been a hair finicky regarding spacing, EOLs, etc.  CA save you from all of that (and is the defacto way to install any docker or plugin application to your server)

 

Is Community Applications supported by Lime-Tech? Preference is to keep system at point of support which is not confused between community support and official support.

 

@dlandon Thanks for additional tests. 

[[6.5.1-rc5] Unable to add docker from existing template.]

See attached. No extra plugins installed. I am trying to install the mariadb from https://github.com/linuxserver/docker-templates/tree/master/linuxserver.io and I get the white screen. I have also noticed that br0 seems to be missing. 

 

I tried 

rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

It had no effect.

cba-unr-01-diagnostics-20180410-0813.zip