-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a tmpfs mount for logs to avoid storage wear #161
Conversation
c36cce1
to
8f9762d
Compare
8f9762d
to
832d532
Compare
3771e26
to
d5e41f8
Compare
I would prefer to limit the tmpfs size to 100MB but the feature was only recently supported in the supervisor and is still not supported in the builder. |
d5e41f8
to
237f5d3
Compare
Your thoughts on this @eiddor? Essentially if we create a tmpfs mount at Pros:
Cons:
I'm tempted to go forward with this even if the tmpfs is larger than we want. This should only be an issue if the logs go crazy and then all of a sudden your device has 50% less memory. On a good day we should never notice the loss of a few hundred megabytes of memory? At least it won't fill your storage and risk bricking your device... |
Traveling so I can't test anything, but I think I'm good with this - We should probably have a recommended memory amount for the project just to avoid some of the smaller devices running into issues on day 1. Is it worth testing this with the bugged version of pihole/PADD just to see the impact when there is a log issue? |
Great idea! Here is a branch with Pi-hole v2022.07.1, PADD v3.8.0 and the tmpfs for logs. It should fill the tmpfs pretty fast and we will see what happens. |
Signed-off-by: Kyle Harding <[email protected]>
237f5d3
to
5b30a68
Compare
The consequences of a full tmpfs seems manageable compared to a full data partition with possible corruption so I'm going to merge this and we can revert it down the road if it adds complications. |
Sounds good! |
Signed-off-by: Kyle Harding [email protected]
Resolves: #131