<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>I've ran into a very rare situation where SQLite3 database corruption occurs on some devices I have deployed.</div><div><br></div><div>I can not guarantee a proper shutdown. The data on the partition is wanted between boots, but not required. When</div><div>I mount it if there is corruption I simply rebuild it. SQLite database corruption can only be detected when using the db file.</div><div>For that I need to create a method to detect it and rebuild the file. That is one solution.</div><div><br></div><div>The next solution is to validate I'm using proper mount options for this partition. </div><div><br></div><div><span style="font-family: Helvetica, Arial, sans-serif; font-size: 14.4444446563721px; line-height: 18.1999988555908px; background-color: #ffffff;" data-mce-style="font-family: Helvetica, Arial, sans-serif; font-size: 14.4444446563721px; line-height: 18.1999988555908px; background-color: #ffffff;"><br></span></div><div>/dev/sda2 on /mnt/nvdata type ext3 (rw,relatime,errors=continue,user_xattr,barrier=0,data=ordered,usrquota,grpquota)</div><div><br></div><div>I'm thinking I need to set barrier to 1?</div><div><br></div><div>Any other things I should consider?</div><div><br></div><div>Chris</div><div><br></div></div></body></html>