Xapian discuss - Jun 2006 - xapian-compact seg faulting & Re: Error msg xapian-compact: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation

xapian-compact with flint db's is still breaking. i tried to more safely
manage the scriptindex process as it built the flint dbs, but seems that
something went awry nonetheless.

thanks


gamma:/index/omega/data# /home/oscar/xapian/bin/xapian-compact -F -m
/svr/hda1/omega/data/bsp0*/default /index/omega/data/bsp0*/default
/svr/hda1/xapian/default
postlist: Reduced by 60.6323% 1074104K (1771504K -> 697400K)
record: Reduced by 51.7614% 98032K (189392K -> 91360K)
termlist .../home/oscar/xapian/bin/xapian-compact: The revision being read has
been discarded - you should call Xapian::Database::reopen() and retry the
operation
gamma:/index/omega/data# 
> ----- Original Message -----
> From: oscaruser@programmer.net
> To: xapian-discuss@lists.xapian.org
> Subject: Re: [Xapian-discuss] xapian-compact seg faulting & Re:
[Xapian-discuss] Error msg xapian-compact: The revision being read	has been
discarded - you should call Xapian::Database::reopen() and	retry the operation
> Date: Wed, 14 Jun 2006 09:22:42 -0800
> 
> 
> OK I'll rerun and report back.
> 
> Thanks
> 
> > ----- Original Message -----
> > From: "Olly Betts" <olly@survex.com>
> > To: oscaruser@programmer.net
> > Subject: Re: [Xapian-discuss] xapian-compact seg faulting & Re: 
> > [Xapian-discuss] Error msg xapian-compact: The revision being 
> > read has been discarded - you should call 
> > Xapian::Database::reopen() and retry the operation
> > Date: Wed, 14 Jun 2006 01:13:08 +0100
> >
> >
> > On Tue, Jun 13, 2006 at 10:38:53AM -0800, oscaruser@programmer.net
wrote:
> > > I am fairly confident that these issues are related to killing
the
> > > scriptindex process ungracefully causing blocks that were queued
for
> > > writing to disk to not get written.
> >
> > The update order is carefully designed such that if the blocks
aren't
> > written, the new version doesn't go live and we stick with the old
one.
> >
> > So I'm doubtful of this explanation.  If you think I'm wrong,
see if
> > you can repeat the problem by interrupting an update...
> >
> > You didn't answer my question about whether this is a one-off
incident
> > or whether it happens if you run the system again from scratch.
> >
> > Cheers,
> >      Olly

-- 
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/