5 ms·
In fact, storage is a big issue. RPI tends to destroy SD card in a way that a cluster like mine isn't exactly safe unless you put high-grade SD card and very re
by stkim1 11y ago
In fact, storage is a big issue. RPI tends to destroy SD card in a way that a cluster like mine isn't exactly safe unless you put high-grade SD card and very reliable power source. Those contribute somewhat higher operation cost which violate the purpose of these single board computer.
- icebraining 11y agoAre you storing the results of computation on the SD cards? Personally, I've mounted every directory that needs to be written to a tmpfs, USB disk or network mount as appropriate, and I've configured fstab to mount the root fs in readonly mode. You can still write by just doing "mount -o remount, rw /" beforehand.
- stkim1 11y agoYes I do. Since Apache Spark is chewing up memory like nothing, I cannot spare any portion of 1G mem for something else. This could lead to a shorter lifespan of SD cards though.
- paulmd 11y agoI've been really unsuccessful at getting a Pi to not destroy SD cards. Good quality cards, good quality power supplies, no swapping - it still eats them up. The best way to fix this is to put the actual OS on an external disk. You absolutely must bootstrap from an SD card, there's no way around that. But that can be entirely read-only and then you bounce to the external drive. Or maybe you could do something like a PXE boot instead - copy a system image down from a server and boot that. Personal opinion, this is the only way I would try using Pis on a long-term basis. The Jetson TK-1 board from NVIDIA includes a real SATA connector. Because it's GPGPU-capable it's also vastly more powerful than even a Pi2. It also has USB 3.0 so running swap on a memory stick would be much more performant.
- sdenton4 11y agoI generally set mine up to use the sd just for boot, and have the actual file system on a usb thumb drive. Works great, and haven't had any sd card corruption issues since I started doing it.