NLS

Yes I know. Problem is how we fight it from within UNRAID. A functionality to ignore brief spikes before reporting... EDIT: Found this and will try the solution proposed...

So I got a new M.2 to replace my previous cache and I noticed that from time to time it just (at idle) "spike" to exactly 84 degrees celcius. But this happens briefly and then it is back to its real idle temp of around 36 degrees. As a result, I get repeated pop-ups and even repeated email reports. Now I can raise the warning level for this disk to be 85 degrees (as 85 is not-perfect-but-survivable for an IC) and be done with it, but is there any other way to resolve this? Like not reporting anything unless it remains for a set time? Help?

No I haven't left it on, on any Android devices. Only two Windows devices (also probably on server's own desktop). A reboot solved it, but still, rebooting for such a thing a production server (esp. with the other issue of huge time-outs during boot for devices with unavailable DNS), is not the best...

So I clicked to see the log (no real reason, nothing seemed out of the ordinary, just clicked it)... And I keep having this in repeat: Nov 24 23:05:33 <my server> nginx: 2022/11/24 23:05:33 [crit] 10373#10373: ngx_slab_alloc() failed: no memory Nov 24 23:05:33 <my server> nginx: 2022/11/24 23:05:33 [error] 10373#10373: shpool alloc failed Nov 24 23:05:33 <my server> nginx: 2022/11/24 23:05:33 [error] 10373#10373: nchan: Out of shared memory while allocating message of size 8539. Increase nchan_max_reserved_memory. Nov 24 23:05:33 <my server> nginx: 2022/11/24 23:05:33 [error] 10373#10373: *1092948 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Nov 24 23:05:33 <my server> nginx: 2022/11/24 23:05:33 [error] 10373#10373: MEMSTORE:00: can't create shared message for channel /disks EVERY SINGLE SECOND! Any ideas? EDIT: Found this: from A YEAR AGO... I do leave dashboard tabs open all the time, both at home and on my work computer... Is this an issue? EDIT #2: And this FROM 4 YEARS AGO! I did have parity check, but it has finished and the entries keep stacking!

There is enough space. I will try. But before I try, is there a way to see real vs claimed size? (to see if I actually succeeded) EDIT: Found it.

I know that, but I don't know how to do it using MC. Also, I don't know what to do NOW that I already copied the files (and already using them). Can I re-shrink them? EDIT: Well, something happened (I also deleted "docker-old" that was the residue of the file copy I did originally, but I don't think this is where the size difference comes from)... and now it is at... 188GB used (probably less than what was on my old disk!). I still want to know if it is possible to shrink down "un-sparsed" VM disks.

OK, thanks (again).

I did, yet I still get an around 5 minute delay in the same place (as shown in my opening post).

I used Midnight Commander as pre-installed on the host machine concole. I am not sure of the parameters it uses when moving and not sure it explains the 120+ GB difference (I have just two VMs on my cache disk). If this is the issue, is it possible I can "re-sparse" the vdisks? On other news, some (but only some) containers presented issues after all, so I re-installed all of them and now it tries to delete the old docker folder (I just renamed it, because it takes WAY too much time to delete - so will delete later)...

I think this has happened before to me, back when I again replaced my cache - but I don't remember how it got resolved (itself?) and can't find any relevant thread. (back then it was from a 500GB SSD to a 500GB NVMe) I am scared if the solution back then was to re-install all my containers... I cannot remember though. So I moved from a 500GB cache drive to a 1TB cache drive. Process went fine (I actually did it my own way, which is just a bit different from the documented ways), which worked fine. My VMs work OK, my dockers too. Thing is, used space in my old 500GB cache, was 47%. So it should be LESS than 250GB of data, right? No new files were written on the cache and it is not from new system files either because I saw the space reported even before enabling VM and docker systems. Even the copy itself (from old to new cache) reported something around 350GB+? Indeed new cache is 39% and reports 388GB of data! (more than 100GB more than the old used space!) Note that I know that 47% (and less than 250GB used) of my old cache were for real, as I happened to use my empty cache space with big file copies that indeed exceeded 200GB (so I was for sure less than 300GB used). Both disks formatted by UNRAID with btrfs. I even scrubbed the new disk. What exactly happened? Is it some kind of deduplication that btrfs will do by itself? Some kind of compression? Something scheduled by filesystem itself? (and in that case can I force it?) Use of "inline" files or sparse files? (note that I use a docker FOLDER not a docker FILE - which means thousands of tiny files) Something else? Any ideas?

I need to wake this up and ask. Did anybody make ANY change regarding this? Because I think no change happened. MyServers did not get updated, nor do I see any relevant change in 6.11.4 and 6.11.5 changelogs. Will anything be actually done?

Let me take the chance to say that you people should try DoubleCommander too. Krusader is good (this is what I used for years), but I think DC is better.

And what is the problem with using 18?

I suggest you move to binhex-crafty-4. All will be better then.

First of all, never make different backups run at the same time. Why would you do that. It is bad practice any way you look at it. Second, no it doesn't make sense for this to happen, except if there is a "restore" somewhere in your schedules. Even if a backup fails, it doesn't mean it would ruin a running source. So, it shouldn't happen and looks like user error to me. If the files were overwritten and you don't have a backup of the version you want, then it's game over for the data. Why you need so many daily backups? Does your minecraft server have that much traffic and changes? How many backups you keep? Because if you keep too few and take backups too many times, then it is also bad practice as you will find yourself even backing up... problems (if you don't find the whatever problem fast enough) and you will not have "clean" backups to revert to.

It is an issue for sure. The delay I get is not just 3 min, it is maybe 10 (or more!), which means that other things that depend on DNS (?) time-out AND THEY DID NOT (I want to point out the difference) before 6.11 (I think). During boot the system should have some backup solution that kicks in early (after testing for DNS maybe). Either use direct IP connections, or have some static hosts or even use 8.8.8.8 (or similar) in case there is no DNS access early in boot. This will probably solve it if DNS is the issue, but will not solve it if gateway is also within the same machine (so be inaccessible during boot) or there is a real Internet issue, or of course someone wants to setup a machine that will be off-internet on purpose (which is something many people don't think much nowadays, but is certainly an option). Whatever the case, the time-outs are HUGE. Even if there is no other solution, if the time outs just become WAY shorter (like 1/3 of what they are), will be a "passable" solution.

One more update and (somewhat) solution. I rebooted. This showed the two plugins as needing an update (properly) and clicking to update them, updates them. So something was stuck. If you ask me, there is a bug somewhere and rebooting in not always a viable solution on a linux based system in production.

Just kicking this up, because it still happens with 6.11.3.

An update on the (still open) issue. Community Apps DID update, because when going to "Apps" tab, it just reports that it is oudated (up in the title). So clicking that, it DOES update. After that, going to plugins shows only two pending (Dynamix File Manager and Unassigned Devices), which I ave no way of changing their status OR removing (to re-add)! So I am in a deadlock! Again, clicking update all plugins, just pops that language pack thing I report above and nothing else. Also note, that the issue is present over more than one computers (and browsers), so it is not related to any stuck cookies or anything like that.

I say it right in the subject. Yes I am in 6.11.3 since yesterday I think. Didn't have that issue with older version. No I don't see any banner in red (like an error?)... neither anything up in the top of the page (the new notification thing). Also (don't know if it is related) scanning my dockers for updates takes FOREVER (several minutes - if it ever finishes). Also note that the server is fresh from reboot (I rebooted for an unrelated reason).

Good tip. I am used to blocks so...

so you see the folders that seem to be too big look in there

Open a terminal, go to offending container and: du -a | sort -n -r | head -n 10 ...to at least know where to look...

It's not just the container's logs, it's also crafty's own logs (there is a logs folder in crafty) AND each server's within crafty, own logs (there is a logs folder within each server)! Seems one of these is bursting with errors. Also, why you have both crafty and crafty 4?