You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Use high endurance varieties of microsd cards. High endurance usually has higher writing capabilities.
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.
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.
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:
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.
The text was updated successfully, but these errors were encountered: