Heater wrote: ↑
Fri Mar 01, 2019 12:18 pm
Put your database on a different media. A USB stick or whatever.
That won't help. The main cause of corruption on abrupt shutdown (unflushed write caches) is present on almost all file systems, regardless of the physical way the storage is connected.
It's made worse on SD card due to their internal workings. Even if linux has flushed its caches the card can still be writing and doing housekeeping (e.g. to support wear leveling) wjen power is removed.
Putting the dabase on a different server may help depending on how you do it. Running the database engine on the server and sending writes as remote operations should be OK. Running the engine locally using files on a network share is likely to still be problematic. You won't get disk corruption but you could still get a corrupted database if power is pulled at the wrong moment.
Attempts to contact me outside of these forums will be ignored unless signed in triplicate, sent in, sent back, queried, lost, found, subjected to public enquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters