3 ms·
I've had a number of Pis (currently 6) in continuous operation around my house for over two years now. One is running http://www.drupalpi.com/ http://www.drupal
by geerlingguy 9y ago
I've had a number of Pis (currently 6) in continuous operation around my house for over two years now. One is running http://www.drupalpi.com/ http://www.drupalpi.com/ currently (uptime was 300+ days until last night when I re-flashed it)... I only use SanDisk Extreme and Samsung Evo+ cards now, but have not had any corruptions on any of these actively-used devices (most are either storing photos (e.g. time-lapse) and then dumping them to the cloud every week or month, or storing time-series data, so there are frequent writes.
I wonder if you could provide what type of card you're using? Also the type and brand of power supply? Besides any of the cheaper cards (basically any brand besides SanDisk and Samsung, it seems) being flaky in my experience, the power supply being flaky (usually when I used a cheap 500 mA supply that came with some device for free) is the only other thing that _ever_ caused corrupt data for me.
- written 9y agoI have similar experience with SanDisk and Samsung EVO+. 9 Pi's (not raspberry) running continuously for ~2 years. No kernel panics/PostgreSQL failures. I run with data checksuming enabled. I also disabled options in PostgreSQL that cause periodic and unnecessary write activity. Frequent regular updates, periodic database activity (web scraping, environment monitoring, ...). Running on F2FS. I have logical replication setup in PostgreSQL, because I don't trust the SD cards anyway, but I have had no issues so far.
- steelframe 9y agoI came here to suggest f2fs. Glad to see you're already doing that.
- written 9y agoIt works surprisingly well and it makes many operations faster than ext4. I noticed it especially when doing system updates. And I've just read yesterday, that F2FS in Linux 4.17 will have further optimizations for low end systems. Yay.