I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Not hugely so, provided it's a good quality card. About 80% of the issues I've had over the years with SD cards being used for Raspberry Pi's have been caused by the Pi itself, but I haven't seen such issues for quite some time. As far as cards actually wearing out, I do regular data verification on pretty much any persistent storage I use, so I catch stuff like that early enough for it to not be an issue about 99% of the time (and Gluster actually makes it pretty easy to rebuild a lost node if you configure it right). On top of that, I'd be using it for a mostly read focused workload, so wearout would probably take longer than it would for most people.
Of course, with USB 3.0 capabilities, that's an alternative option, though I actually trust SD cards a bit more than USB flash drives, and I wouldn't even begin to consider using an external enclosure (too easy to accidentally bump the Pi or the enclosure and cause a USB bus reset, which is not something Linux will usually gracefully recover from if you're actively using the storage space).
Of course, with 4G of RAM and GbE, I might consider getting one or two to use a native ARM virtualization hosts. I do a lot of cross-distro software verification, and a Pi running QEMU at 1.5GHz can probably beat my main virtualization system emulating an equivalent ARM CPU in terms of raw performance.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not hugely so, provided it's a good quality card. About 80% of the issues I've had over the years with SD cards being used for Raspberry Pi's have been caused by the Pi itself, but I haven't seen such issues for quite some time. As far as cards actually wearing out, I do regular data verification on pretty much any persistent storage I use, so I catch stuff like that early enough for it to not be an issue about 99% of the time (and Gluster actually makes it pretty easy to rebuild a lost node if you configure it right). On top of that, I'd be using it for a mostly read focused workload, so wearout would probably take longer than it would for most people.
Of course, with USB 3.0 capabilities, that's an alternative option, though I actually trust SD cards a bit more than USB flash drives, and I wouldn't even begin to consider using an external enclosure (too easy to accidentally bump the Pi or the enclosure and cause a USB bus reset, which is not something Linux will usually gracefully recover from if you're actively using the storage space).
Of course, with 4G of RAM and GbE, I might consider getting one or two to use a native ARM virtualization hosts. I do a lot of cross-distro software verification, and a Pi running QEMU at 1.5GHz can probably beat my main virtualization system emulating an equivalent ARM CPU in terms of raw performance.