Hello all, We have experienced repeated database corruption issues after upgrading from 1.4.196 tot 1.4.199. The scenario is always the same:
- the application uses an embedded file-based database (MVStore, close to 500Mb) - the application is stopped (kill on linux, normal shutdown, no kill -9) - the database is backed up - the application is restarted and reconnects to the database - the database is corrupted (not ever time but about once in 10 times) org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalStateException: Reading from nio:/path/database.mv.db failed; file length -1 read length 384 at 250535725 [1.4.196/1]"; This process has worked without issues for years now, with various versions of H2. Only after a recent upgrade to 1.4.199 have we experienced multiple database corruptions. What strikes me is peculiar is that H2 version mentioned in the error message. The database was indeed created with 1.4.196. Is there something that has changed in this area? Should we recreate the database? -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
