This looks very much like a temporary table issue Thomas fixed in
1.3.172, which might be why I'm not seeing it.
Can you check again on 1.3.172?
On 2013-06-11 17:20, Andrew Helgeson wrote:
Noel,
The initial problem was discovered on a linux server running kernel
3.2.1, java version 1.6.0_31 and a raid 1 array of ssd's. I have run
this test case on a Macbook Air using the internal ssd as well as an
attached HDD, both times corrupting. With the default settings in the
test case, it will always corrupt some point after 500 rows but it can
sometimes take closer to 1500, it appears to be a race condition.
While the initial problem has been encountered on several versions of
h2, I have only tested this case on 1.3.170. My java version is 1.6.0_45.
Here is the error I encounter:
Caused by: org.h2.jdbc.JdbcSQLException: General error:
"java.lang.RuntimeException: old!=record pos:535 old:page[535] data
leaf table:704 TEMP_RESULT_SET_704 entries:0 parent:0 keys:null
offsets:null new:page[535] data leaf table:20 T_TBL2 entries:1
parent:524 keys:[971, 0, 0, 0, 0] offsets:[2042, 0, 0, 0, 0]"; SQL
statement: INSERT INTO t_tbl2 (age_fk) values (42) [50000-170]
Thanks
On Tuesday, June 11, 2013 4:07:16 AM UTC-5, Noel Grandin wrote:
On 2013-06-10 22:12, Andrew Helgeson wrote:
>
> The corruption has been encountered on versions 1.3.163/170/172
of H2.
> Once the database has reached this state it cannot be dumped.
>
Your test case is working fine for me, tested on two different
storage
devices.
Have you tried testing on different machines?
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
