You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a "no-reserve" (aka "use full space") option was enabled for a v2.5 database, then the issue becomes visible right after restore on v3.0, just do an immediate validation and see:
Summary of validation errors
Number of database page errors : 90167
Then check firebird.log and see:
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: Page 1017 wrong type (expected SCN inventory encountered purposely undefined)
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: SCN's page 1017 {sequence 1} inconsistent
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: Page 2034 wrong type (expected SCN inventory encountered purposely undefined)
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: SCN's page 2034 {sequence 2} inconsistent
and so on. Only SCN pages are corrupted, they are all unexpectedly zeroed.
It means that only incremental restore is affected by this issue, basically the database operates OK. A short-term workaround is: gfix -use reserve + backup/restore.
Submitted by: @dyemanov
If a "no-reserve" (aka "use full space") option was enabled for a v2.5 database, then the issue becomes visible right after restore on v3.0, just do an immediate validation and see:
Summary of validation errors
Number of database page errors : 90167
Then check firebird.log and see:
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: Page 1017 wrong type (expected SCN inventory encountered purposely undefined)
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: SCN's page 1017 {sequence 1} inconsistent
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: Page 2034 wrong type (expected SCN inventory encountered purposely undefined)
solaris Sat Aug 13 18:01:28 2016
Database: /work/data/abc.fdb
Error: SCN's page 2034 {sequence 2} inconsistent
and so on. Only SCN pages are corrupted, they are all unexpectedly zeroed.
It means that only incremental restore is affected by this issue, basically the database operates OK. A short-term workaround is: gfix -use reserve + backup/restore.
Commits: 610594a 02d9e44 408dff8 3ba0eb1
====== Test Details ======
NB: could not get validation errors using steps described by hvlad. Confirmed bug if use .fbk from 2.5.x and restore it.
The text was updated successfully, but these errors were encountered: