Skip to content
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

Suggestion: #91

Open
quarky42 opened this issue Jun 11, 2023 · 0 comments
Open

Suggestion: #91

quarky42 opened this issue Jun 11, 2023 · 0 comments

Comments

@quarky42
Copy link

Please consider adding something to the readme about the life expectancy of a microsd card when writing very active log files to it.

If you aren't already aware, microsd cards have a finite number of write cycles. Many, like the Samsung Evo Select, can do 10,000 write cycles before the card is worn out. Log file writing means than there are many write operations which can shorten the life of the memory card.

With my main concern being reliability, I would suggest that people either:

  1. Use high endurance varieties of microsd cards. High endurance usually has higher writing capabilities.
  2. Use a USB drive, preferably a USB SSD (which has a finite number of write cycles. Some SSDs can go up to 1,000,000 write cycles. You can simply symlink the config directory to the USB drive's mount point.
  3. You can use a ramdisk for the logs instead. If you're wanting to keep the logs, a cron job that copies them to a microsd location once per hour would take over a year to write 10,000 times. The life of the microsd might be diminished by very small amount considering the size of the logs.

Here is a guide I used to setup the ramdisk:
https://ostechnix.com/how-to-write-log-files-in-ram-using-log2ram-in-linux/

Combine this with logrotate to remove logs older than 30 days, or whatever amount you want to keep and you'll have yourself a pretty reliable setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant