I occasionally see this failure:
6: lsm, row-store t, file:wt-000001.lsm, session.verify: RUNDIR/wt-000001.lsm: No such file or directory t: session.verify: table:wt: post-salvage verify: No such file or directory
and:
t: salvage: dump comparison failed: Unknown error: 256
which is from this code:
/* * If no records are deleted, we can salvage the file and test * the result. (The problem with deleting records is salvage * restores deleted records if a page splits leaving a deleted * record on one side of the split.) * * Salvage, verify the salvaged files, then dump (comparing * against the Berkeley DB data set again, if possible). */ if (g.c_delete_pct == 0) { wts_open(g.home, 1, &g.wts_conn); wts_salvage(); wts_verify("post-salvage verify"); wts_close(); wts_dump("salvage", SINGLETHREADED); }
Michael's change in 07691a5 turns off the salvage step, but then the subsequent verify and dump calls are failing.
- related to
-
WT-1 placeholder WT-1
- Closed
-
WT-2 What does metadata look like?
- Closed
-
WT-3 What file formats are required?
- Closed
-
WT-4 Flexible cursor traversals
- Closed
-
WT-5 How does pget work: is it necessary?
- Closed
-
WT-6 Complex schema example
- Closed
-
WT-7 Do we need the handle->err/errx methods?
- Closed
-
WT-8 Do we need table load, bulk-load and/or dump methods?
- Closed
-
WT-9 Does adding schema need to be transactional?
- Closed
-
WT-10 Basic "getting started" tutorial
- Closed
-
WT-11 placeholder #11
- Closed
-
WT-12 Write more examples
- Closed
-
WT-13 Define supported platforms
- Closed
-
WT-14 Windows build
- Closed
-
WT-15 Automated build/test infrastructure
- Closed
-
WT-16 Test suite
- Closed
-
WT-972 test/format failing to salvage LSM trees
- Closed
-
WT-976 format checksum error
- Closed