src

Unraid is used in countless different ways, including home, home lab, and business. If LimeTech really only expected UnRaid to be used as a "home NAS product", they wouldn't be increasing the costs to their users by changing to a recurring fee license. I know you just want me to "get over it", but sorry, no. This was inappropriate. This was pushing unnecessary, non-function-enhancing code onto my server for no good reason other than "for the LOLs". Obviously, some people liked it. OK, fine. Obviously, some people didn't care either way. OK, fine. But, also obviously, some of us object to PRANKS ON OUR INFRASTRUCTURE. Not OK. Not fine. You don't get to hand-wave away our concerns just because you don't care. It is not incumbent on us to accept your lack of concern as a valid reason not to complain about this. If LimeTech really doesn't care about these concerns, that's THEIR choice to make. Not yours, not mine. If they choose to continue in this vein, then my choice will be to take my business elsewhere. That's not a threat or anything, that's just the way all this works. They already have my money for my Pro license, so losing me won't matter to them in a fiscal sense. But if they won't take their customers seriously going forward, I won't be able to consider them a serious option.

I'll just finish out by saying that April 1 is an opportunity, NOT an obligation. There are plenty of people to be pranked who are not your paid customers running your mission critical software on OUR hardware. Especially a prank that appears, at first glance, to indicate that something has gone seriously wrong with that software or the backing infrastructure. The tech world seems to take April 1 as some sort of "global challenge day". But it's not. it has turned into a day I dread, because every company/site wants to prove how clever and "fun" they are - yet often prove the opposite. Prank your friends. Prank your family. Prank your co-workers. But in the future, please leave my server out of it.

Reposting here from my original in General Support: I know it's April 1, but please, PLEASE, in the future restrain yourselves from trying to come up with a funny hack for MY SERVER SOFTWARE. Write a funny blog post. Make a crazy product announcement. Whatever. But never, EVER, mess with the CRITICAL software that we depend on. Would you enjoy waking up to find that your all your phone's contacts were renamed, "just for fun"? Or all your Windows icons? Well, just imagine my joy late last night when I got the monthly "these things should be updated" email from my server, logged in, and saw RANDOM FACES instead of app icons. Was there a hack on the Docker servers? On Unraid? What the heck was happening? Oh, yeah, sit there and chuckle at your great cleverness. Or don't. This isn't a toy, this isn't some unimportant little side-app. This is server software, and it should be immune to these kinds of too-clever-by-half "pranks". Find another way to prove to the world you have whimsy. ---- One of the things that REALLY bothers me about this is that they added NEW CODE to make this happen. At some point, somewhere, code was added to the system that enabled this. It looks like it was in the Community Apps plugin, but still that's code that is running on our UnRaid instances. As a professional software developer (yeah, appeal to authority, I know), this is deeply disturbing. This was essentially a "hidden feature" that nobody knew was being installed on our servers. Adding "joke" code is a bad idea in general. Adding it to a server can lead to potential security vulnerabilities. Pretty much ANY new code can lead to vulnerabilities through unintended consequences, so adding something like this rubs me the wrong way on so many levels.

It's an April Fools thing, and incredibly inappropriate to put onto our servers.

One of the things that REALLY bothers me about this is that they added NEW CODE to make this happen. At some point, somewhere, code was added to the system that enabled this. It looks like it was in the Community Apps plugin, but still that's code that is running on our UnRaid instances. As a professional software developer (yeah, appeal to authority, I know), this is deeply disturbing. This was essentially a "hidden feature" that nobody knew was being installed on our servers. Adding "joke" code is a bad idea in general. Adding it to a server can lead to potential security vulnerabilities. Pretty much ANY new code can lead to vulnerabilities through unintended consequences, so adding something like this rubs me the wrong way on so many levels.

I know it's April 1, but please, PLEASE, in the future restrain yourselves from trying to come up with a funny hack for MY SERVER SOFTWARE. Write a funny blog post. Make a crazy product announcement. Whatever. But never, EVER, mess with the CRITICAL software that we depend on. Would you enjoy waking up to find that your all your phone's contacts were renamed, "just for fun"? Or all your Windows icons? Well, just imagine my joy late last night when I got the monthly "these things should be updated" email from my server, logged in, and saw RANDOM FACES instead of app icons. Was there a hack on the Docker servers? On Unraid? What the heck was happening? Oh, yeah, sit there and chuckle at your great cleverness. Or don't. This isn't a toy, this isn't some unimportant little side-app. This is server software, and it should be immune to these kinds of too-clever-by-half "pranks". Find another way to prove to the world you have whimsy.

The normal reason for using this setting would be when you do not currently have a cache disk but intend to add one later. I must be having a serious density issue at the moment, because that still doesn't make sense to me. Now that I know that this functionality exists, the only thing I can think of would be to move data to a faster drive for performance reasons (database, etc.), especially avoiding parity overhead during write operations.

Yeah, I totally misunderstood what the Prefered cache setting for the shares does. I expected the Cache settings to only affect new files copied to the array. Going back and re-reading the help, I now see that it says (for Prefer) "When the mover is invoked, files and subdirectories are transfered off the array and onto Cache disk/pool". I misread that because I never considered a use-case for copying files from the array to the cache for long term storage.

I've tried to search for this, and hope I haven't missed anything obvious, but I just rebuilt my unRAID system and added a cache drive. Everything went reasonably well, but after setting up the cache drive it immediately filled up with data from my data drives. I haven't copied anything new to the system yet, but the cache drive seems to be constantly churning, as if it is moving data off from the data drives to the cache drive, and then back to the data drives. Is there some sort of automatic re-balancing of my data drives that's causing this, or is there something else going on? How can I control this behavior? Thanks!