db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maciek Makowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6425) DB got corrupted during the heavy operations.
Date Wed, 10 Dec 2014 16:14:13 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241308#comment-14241308
] 

Maciek Makowski commented on DERBY-6425:
----------------------------------------

I ran into this (or a very similar) issue in a test where the process running embedded Derby
under high load is forcibly killed (SIGKILL) dozens of times per hour. On average once every
1200 such kills I get the "XSDG2: invalid checksum" error. This renders the database unusable,
i.e. the error is thrown when a JDBC connection is being created, so I can't inspect anything
or recover the data.

I have confirmed this to occur in the following versions of Derby:

* JavaDB distributed with Oracle JDK 1.7.0_51
* 10.10.1.1
* 10.11.1.1

Note that I do run with write cache enabled, but the OS or hardware itself is not being shut
down when the corruption occurs. Can anyone explain why the data that was supposed to be written
would not make it to the disk in this scenario?

Please let me know if there is any additional information that could help pinpoint and resolve
this issue.

> DB got corrupted during the heavy operations.
> ---------------------------------------------
>
>                 Key: DERBY-6425
>                 URL: https://issues.apache.org/jira/browse/DERBY-6425
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.9.1.0
>         Environment: Suse 10.
>            Reporter: patil devidas
>            Priority: Critical
>
> ------------  BEGIN SHUTDOWN ERROR STACK -------------
> ERROR XSDG2: Invalid checksum on Page Page(5482,Container(0, 2032)), expected=3,506,219,016,
on-disk version=492,279,644, page dump follows: Hex dump:
> 00000000: 0075 0000 0001 0000 0000 0000 0067 0022  .u...........g..
> 00000010: 0000 0028 0000 0000 0000 0000 0000 0000  ................
> 00000020: 0000 0000 0001 0000 0000 0000 0000 0000  ................
> 00000030: 0000 0000 0000 0000 0000 0000 0406 000a  ................
> 00000040: 0026 0024 6139 3630 3261 6266 2d33 3163  ....a9602abf.31c
> 00000050: 662d 3131 6533 2d38 3363 632d 6231 3935  f.11e3.83cc.b195
> 00000060: 6138 3139 3263 6334 000b 0009 434f 4d50  a8192cc4....COMP
> 00000070: 4c45 5445 4400 0c07 dd0a 0a00 1310 0c05  LETED...........
> 00000080: 4e08 4000 0c07 dd0a 0a00 1310 1c03 1975  N..............u



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message