Quite a lot of writes to SSD cache, how identify? (looks like writes to docker.img)


44 posts in this topic Last Reply

Recommended Posts

I do worry a bit about the solution as this guy 'lost' his dockers. Which would in my case mean I lose most of the Home Assistant configuration (not configuration files, but things like built-in integrations, internal user settings etc.)

On 5/12/2020 at 7:28 PM, hovee said:

I tried following your tutorial, but after reboot it tells me I don't have any docker containers installed.

1065017496_ScreenShot2020-05-12at1_22_45PM.thumb.png.a9d6bea9fabc2f755b413d1a8194d734.png

 

It shows me the docker service is running.

1044152176_ScreenShot2020-05-12at1_23_04PM.thumb.png.e8e5a1ae8b047b3c68eb9e1a136bebfd.png

 

Checking the logs I can see it created the softlinks.

490799377_ScreenShot2020-05-12at1_24_39PM.thumb.png.be86bce91c4fb763629d4be5611bcfda.png

 

If I remove that entry to copy the rc.docker file in the /boot/config/go directory everything works again after a reboot. However, then it puts it back to original and uses loop2.

Link to post
6 minutes ago, maxstevens2 said:

I do worry a bit about the solution as this guy 'lost' his dockers. Which would in my case mean I lose most of the Home Assistant configuration (not configuration files, but things like built-in integrations, internal user settings etc.)

 

You don't need the solution mentioned there if running 6.9-rc2. In 6.9 you can select a dir to store your docker data instead of the docker.img (in the gui).

You will lose all of your dockers but you can easily add them back with all your settings intact by using the "ADD CONTAINER" button. Select your docker from the "Template:" dropdown box and click apply.

Edited by Niklas
Link to post
2 minutes ago, Niklas said:

 

You don't need the solution mentioned there if running 6.9-rc2. In 6.9 you can select a dir to store your docker data instead of the docker.img in the gui.

You will lose all of your dockers but you can easily add them back with all your settings intact by using the "ADD CONTAINER" button. Select your docker from the "Template:" dropdown box and click apply.

 

Has 6.9 been stable for you? Been waiting for the new big release, but if it stable and the docker can be fixed, that would be perfect!

Link to post
2 minutes ago, maxstevens2 said:

 

Has 6.9 been stable for you? Been waiting for the new big release, but if it stable and the docker can be fixed, that would be perfect!


57 days uptime without any problems. I just moved from docker.img to directory like three hours ago, running fine. 

 

5 minutes ago, jay010101 said:

Hey guys. I had this issue and moved to the newest beta and it was fixed. You can also use the below command but its not persistant after boot.

 

mount -o remount -o space_cache=v2 /mnt/cache

 

 

I hope this helps


As i understand, that command is not needed anymore with the 6.9-rc2. It only mitigates some of the writing amplifications but it's a start. :)

Edited by Niklas
Link to post

Here it's now 23:29. So I am trying to get this fixed before Monday morning. I will update Unraid asap.
I will ofcourse backup the image and such.

 

8 minutes ago, Niklas said:

You will lose all of your dockers but you can easily add them back with all your settings intact by using the "ADD CONTAINER" button. Select your docker from the "Template:" dropdown box and click apply.

 

Is there a way to transport/move the dockers from the img to the 'new location'? Or is what you said the way to get the docker back with it's settings?

Link to post
1 minute ago, maxstevens2 said:

Here it's now 23:29. So I am trying to get this fixed before Monday morning. I will update Unraid asap.
I will ofcourse backup the image and such.

 

 

Is there a way to transport/move the dockers from the img to the 'new location'? Or is what you said the way to get the docker back with it's settings?


Same time-zone as me.
Yes, that what I said. You can try the "add container" button now before upgrading and you will probably see what I mean. Your dockers with settings will be in the "Template:" dropdown list (under "User templates").

Link to post

I might have found out that Home Assistant doesn't actually 'abuse' the docker image file as it's storage location. So I am more hopeful now. Will now shut dockers down and backup the image. Then need to have 1 docker online at 00:00 CET. After that upgrade time. I'll keep you updated lol.

Thanks for the help so far though!!

Link to post
8 minutes ago, maxstevens2 said:

I might have found out that Home Assistant doesn't actually 'abuse' the docker image file as it's storage location. So I am more hopeful now. Will now shut dockers down and backup the image. Then need to have 1 docker online at 00:00 CET. After that upgrade time. I'll keep you updated lol.

Thanks for the help so far though!!


Also running home assistant. The most abuse I saw was writing to the home-assistant_v2.db (recorder/history). I moved home-assistant_v2.db from the btrfs cache to my unassigned hdd in 6.8.3. With the multiple cache pool support in 6.9, I removed unassigned devices and added the hdd as a second cache pool formatted as XFS. Just for use with stuff that writes lots of data to save some ssd life. No critical stuff.

 

Capture_ServerUpdateContainer_-_Google_Chrome_2021-02-28_23-55-31_92567105.thumb.png.c162aea7132f6da51427e121c1c52ef3.png

Link to post

Ah, my recorder/database for history is stored in MariaDB on docker... which is kinda how this all started.
You might believe it is stupid to run it like that, but it ran on MariaDB inside a VM for months without any crazy writes on an old HDD... But I won't get too database'y. Time to upgrade now though!

Link to post
38 minutes ago, maxstevens2 said:

Is there a way to transport/move the dockers from the img to the 'new location'? Or is what you said the way to get the docker back with it's settings?

Rather than try and save the docker.img, just recreate it.  Less hassles.

 

Also, far easier rather than doing Add Container to add them back in one at a time to instead Apps, Previous Apps and check off what you want then hit Install.  

Link to post

So, Unraid updated quite easily. Only issue now is the following, but won't matter too much as 4/7 are just barebone nothing lol:

afbeelding.thumb.png.adf9b8ad5b4195b4f2ea83fb84b16779.png

 

The rest of the 'fixes' I will try tommorow (a.k.a. today) as the dockers don't impact a lot, but the VM's do. Will work on it later though.

Weirdly the writing (according to Unraid's UI) doesn't seem to be in use that crazy much right now. Nearly 3MB/s write peak instead of 25 MB/s. See picture after (red line is the kinda docker-started line):
afbeelding.thumb.png.27fb7101ae2ea36dcc38398c466ce8f7.png

 

Before the update it litterally spiked continously from 12 to 2 to 25 and sometimes (server at high-performance) to 54.
Will very much keep an eye for it for now. Maybe I don't even need to change it. Or you guys have suggestions?

 

Really have to give out probs already to @Niklas with the update suggestion. Otherwise I would have needed to apply the solution in the 'report' page 2.
Good Nighty :')
 

Link to post
16 minutes ago, Squid said:

Rather than try and save the docker.img, just recreate it.  Less hassles.

 

Also, far easier rather than doing Add Container to add them back in one at a time to instead Apps, Previous Apps and check off what you want then hit Install.  


Far easier, yes. I knew I had that information somewhere locked away in my brain. Thanks for pointing that out!
I just moved from docker.img to directory and added my 20 containers back using the add container button. Wasted some time there. ;) 

Link to post
20 minutes ago, maxstevens2 said:

Maybe a bit off topic, but do you use dockers for Home Assistant MQTT @Niklas? My power usage is now litterally showing in kind off encrypted style in the log. lol
afbeelding.png.7c04a8aae88486a672867db98bba2091.png

Only when I am not on the website it won't show anything.. xD

 

Not using MQTT (yet).

I think it has something to do with networking. I don't know if this bug report could help 

 

Link to post
7 hours ago, maxstevens2 said:

Really have to give out probs already to @Niklas with the update suggestion. Otherwise I would have needed to apply the solution in the 'report' page 2.

 

The GO (and service.d file) modifications are not needed anymore in unraid 9.2 as they basically created a way to do exactly that from the GUI.

The GUI should now allow you to host docker files in their own directory directly on the cache (which what the workaround did via scripts instead of the GUI).

Haven't moved there myself yet as I still see enough issues with rc2 for now.

I believe that reformatting the cache is also advisable cause they have made some changes in the partition alignment there as well (you may or may not get lesser rights because of it, I'm using Samsung EVO's so I consider wiping and reformatting mine after the upgrade).

 

Cheers!

Link to post

So comming back to this now. I changed a few local things.

- I've updated Unraid to the 6.9-rc2.

- Home Assistant now only saves every 30 seconds to the database.

 

I came up with these results in a 34 minute timepsand:

afbeelding.png.9422fdbbf07bdde2494e8b10fbfcb011.png

 

All calculated, this generates around 47 GB of writes a week, which I find more casual for the disk (due to there being 3 of them).

Recalculated this is around 4.7 Megabyte per minute and 0,07 per second (and around 0,149 on the btrfs-transacti).

A yearly sum of this woul be around 2466 GB of writes (docker only). I think this is a need fit compared to the 20+ MB/s before nearly being continously. Which would be 1,296 (or just 1,2) TERABYTE per day at 15MB/s 24/7.

 

As of now and the thing I reported earlier, I actually broke the log (/var/syslog is just empty). I guess this doesn't affect loopt but I will retest.

 

 

Edit:

Here you can clearly see the 30 seconds mark when Home Assistant Pushes its data out. Before the saving rate was every 10 seconds

afbeelding.thumb.png.02a69c1c5a870640ea3c822418610482.png

Edited by maxstevens2
Link to post

Got it all fixed now, no crazy writes anymore, and no crazy action.

 

I do try to make the usage of the MariaDB as little as i can, but still have some performance. So I won't cache like 15 minutes and then drop it all at once onto the databases.

 

For anyone wondering I've applied the following workaround for the insane logging:

Just now, maxstevens2 said:

Hi, I've been on the same issue. An 'easy way' to fix this (temporarely, but without crazy always runnings scripts) is by adding something in the blacklist of rsyslogd. In my case I added the following:

 


:msg,contains,"tun:"


KEEP IN MIND THAT I ADDED, NOT REPLACED. There were 2 other lines in the file for me:

:msg,contains,"Error: Nothing to do" stop
:msg,contains,"user \"logout\" was not found in \"/etc/nginx/htpasswd\", client" stop

 

Hope someone can use this info as workaround. I really couldn't change anything like said before, it would ruin the dockers functions due to local network scans.

 

Very happy with the solution right now.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.