Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of crspan@gmail.com designates
 64.233.178.249 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=Lrph80fXPZEJPMZtv9vK4l/cMIE92bzdPS7+GlWCfYcq7XavlY2xPxxeJp4T2UKxW3uCSU51v8CDU2Vc2AaXB83mQHp2gLIOPLevTbs1T7hFAUIjGnsX8ozmo/skXDIds7VaZoXtquRDJobS5wR72Vlw+vgIRk3+zXX4bmpNhX4=
Message-ID: <4821CB9B.7040104@gmail.com>
Date: Wed, 07 May 2008 10:32:43 -0500
From: crspan <crspan@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Michael McCandless <lucene@mikemccandless.com>
CC: java-user@lucene.apache.org
Subject: Re: Are those runtime errors about the jdk, or lucene's jar, or my
 code?
References: <48209D62.2000103@gmail.com>
 <D0DBD255-D484-481B-88E1-A4D8BF5BE038@mikemccandless.com>
 <48212BEB.50801@gmail.com>
 <11EFE28B-E740-4D51-A6E5-DDFAE3B47188@mikemccandless.com>
In-Reply-To: <11EFE28B-E740-4D51-A6E5-DDFAE3B47188@mikemccandless.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Exactly the case you have described. Not sure why it got corrupted after 
scp. IF compare the index size, exact bytes. But I also noticed that the 
scp process was dangling there long after, so I killed that process. 
Maybe that is why.

    Lesson learned: Still "CheckIndex", even index size matches.

Thanks again, Mike.

Charlie


Michael McCandless wrote:
>
> OK, phew.  Thanks for bringing closure here.
>
> You mean you ran CheckIndex on the original index (input to scp) and 
> it was fine, but CheckIndex on the copy produced by scp showed the 
> corruption?
>
> I think it's unusual for scp to corrupt the copy unless something 
> catastrophic happens (eg disk full, disk is bad, RAM is bad, etc.).
>
> Mike
>
> crspan wrote:
>> Thanks so much, Mike. Those runtime errors were caused by one 
>> corrupted index, somehow corrupted during scp. It has Nothing to do 
>> with lucene 2.3.2.
>>
>> For those who come by this thread:
>>       Please "CheckIndex"
>>
>> That would saved me many hours of fruitless debugging.
>>
>> Cheers,
>> Charlie
>>
>>
>> Michael McCandless wrote:
>>>
>>> Hi,
>>>
>>> Could you run org.apache.lucene.index.CheckIndex on your index and 
>>> post the result?
>>>
>>> Are these exceptions easily reproduced starting from scratch (new 
>>> index)?
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org