Dear list, Harddrives can fail in the most remarkable, surprising ways imaginable, as for instance reflected on https://www.usenix.org/legacy/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/index.html and https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ .
(E.g., writes may fail transparently, random sectors may be zeroed, the disk's internal sector map may break so reads may return any garbled data, RAM-based disk cache may hide write failures so data initially seems to have been written but was not, etc.) This motivates me to ask for your complete answer to, 1) What is the worst-case SQLite misbehavior(s) that can disk failure can lead to, and, 2) Through what return values and otherwise does SQLite report non-exotic disk failures, and, 3) In a server setup, is there any panacea against disk failures - basing the storage on RAID1 perhaps? Thanks, Mikael
