Hi Piret, Have you attempted a "Crash Recovery When The Normal Crash Recovery Fails” which rebuild schema and system keys etc as detailed in the docs at:
http://docs.openlinksw.com/virtuoso/backup_recovery/
<http://docs.openlinksw.com/virtuoso/backup_recovery/>
as I don’t see why you cannot try this ?
Also, do you have "Log Audit Trail" and "On-line Backups" enabled as indicated
the backup docs above, which is always recommend such you can can always
recover to the last known good state of the database ?
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter -- http://twitter.com/OpenLink
Google+ -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers
> On 2 Sep 2016, at 09:26, Piret Lattikas <piret.latti...@zerotech.ee> wrote:
>
> Hi, Hugh.
>
> Thank you for your response.
>
> Yesterday evening another virtuoso crashed during the backup set by
> virtuoso inner scheduler with the same error:
> ....
> 20:13:12 Backing up page 2930000
> 20:13:12 page set checksum ck=d368ab6a pck=5368ab6a xor = 80000000
> 20:13:12 /usr/bin/virtuoso-t() [0xb07467]
> ....
> 20:13:12 /usr/bin/virtuoso-t() [0xb15a4c]
> 20:13:12 /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7ff19d613182]
> 20:13:12 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7ff19cc1d47d]
> 20:13:12 GPF: disk.c:298 page set checksum error
>
> Today I run the integrity check as you suggested and it also stopped
> with the following error:
> ....
> 07:57:36 Backup to /dev/null started
> 07:57:36 Dumping the schema tables
> 07:57:36 Dumping the registry
> 07:57:36 Dumping the schema done
> 08:05:05 /usr/bin/virtuoso-t() [0xb07467]
> ....
> 08:05:05 /usr/bin/virtuoso-t() [0xb15a4c]
> 08:05:05 /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7fb0752c9182]
> 08:05:05 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fb0748d347d]
> 08:05:05 GPF: page.c:899 out of order
>
> Suggesting that our virtuoso is corrupt, but making a crash dump is not
> an option for us due to the error in the database after restoring with
> date fields, that I have reported already.
> The previous virtuoso-users mail list thread:
> https://www.mail-archive.com/search?l=virtuoso-users@lists.sourceforge.net&q=subject:%22Re%5C%3A+%5C%5BVirtuoso%5C-users%5C%5D+SQL+Error+on+insert+with+virtuoso+7.2.1%22&o=newest.
>
> AS I remember I sent a test scenario how I could reproduce it to
> Patrick, but have not gotten any feedback on the matter yet.
>
> The version of virtuoso:
> # virtuoso-t -?
> Virtuoso Open Source Edition (Column Store) (multi threaded)
> Version 7.2.3-dev.3215-pthreads as of Jan 20 2016
> Compiled for Linux (x86_64-pc-linux-gnu)
> Copyright (C) 1998-2015 OpenLink Software
>
> What can cause the "page.c:899 out of order" corruption, to know how to
> avoid it? We have been using virtuoso for some time without any problems.
>
> Best regards.
>
> Piret
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
