[Xapian-tickets] [Xapian] #592: (crash) ChertTable::add_item_to_block on a seemingly corrupted block

Xapian nobody at xapian.org
Tue Mar 27 15:57:12 BST 2012


#592: (crash) ChertTable::add_item_to_block on a seemingly corrupted block
---------------------------+------------------------------------------------
 Reporter:  static-void    |       Owner:  olly 
     Type:  defect         |      Status:  new  
 Priority:  normal         |   Milestone:       
Component:  Backend-Chert  |     Version:  1.2.5
 Severity:  normal         |    Keywords:       
Blockedby:                 |    Platform:  Linux
 Blocking:                 |  
---------------------------+------------------------------------------------

Comment(by static-void):

 Xapian-check does report an error:

 {{{
 record:
 baseB blocksize=8K items=23132 lastblock=42 revision=3865 levels=1 root=42
 B-tree checked okay
 record table structure checked OK

 termlist:
 baseB blocksize=8K items=46264 lastblock=2175 revision=3865 levels=2
 root=2172
 B-tree checked okay
 termlist table structure checked OK

 postlist:
 baseB blocksize=8K items=15549 lastblock=698 revision=3865 levels=2
 root=10
 B-tree error 90
 xapian-check: btree error
 }}}

 I've tried to move the index dir away, so that zeitgeist would initiate a
 re-index. The resulting index is ok:

 {{{
 record:
 baseB blocksize=8K items=24913 lastblock=37 revision=3 levels=1 root=14
 B-tree checked okay
 record table structure checked OK

 termlist:
 baseB blocksize=8K items=49826 lastblock=2146 revision=3 levels=2 root=631
 B-tree checked okay
 termlist table structure checked OK

 postlist:
 baseB blocksize=8K items=16622 lastblock=964 revision=3 levels=2 root=5
 B-tree checked okay
 postlist table structure checked OK

 position:
 baseB blocksize=8K items=635149 lastblock=1765 revision=3 levels=2
 root=639
 B-tree checked okay
 position table structure checked OK

 spelling:
 Lazily created, and not yet used.

 synonym:
 Lazily created, and not yet used.

 No errors found
 }}}

 Currently, I see no way to find out how it became corrupted. I guess I
 will just run zeitgeist normally and check if the issue would appear
 again. I left the old copy of the index as it is, if its of any interest.

-- 
Ticket URL: <http://trac.xapian.org/ticket/592#comment:3>
Xapian <http://xapian.org/>
Xapian



More information about the Xapian-tickets mailing list