[
https://issues.apache.org/jira/browse/DERBY-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241354#comment-14241354
]
Mike Matrigali commented on DERBY-6425:
---------------------------------------
I also assumed that if a machine did not crash that write caching would not be
an issue. But since write caching
is not supported for derby we have never tested it.
I did consult once with someone who has a low level device using derby that was
seeing similar errors on a forked
and changed copy of the code, but I think they were actually crashing the
hardware often. I think what they did was to make sure that their derby table
page size was equal or smaller to their filesystem block size and they stopped
having problems.
> 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)
