The traceback is truncated? Still, this looks like your filesystem (and, specifically at least one of the files it's holding for Lucene) is corrupted -- Lucene was trying to read bytes from a file, in order to merge segments, and the OS/IO system threw that exception.
You should run CheckIndex (which should detect & describe the corruption), and then try to recover the index by re-running CheckIndex with -fix. But, more importantly, you need to figure out why your filesystem has developed corruption because it will likely happen again! Mike On Thu, Apr 15, 2010 at 3:31 AM, liat oren <oren.l...@gmail.com> wrote: > Hi All, > I got the following error while trying to optimize index sized 31 GB: > Exception in thread "Lucene Merge Thread #3" > P.Lucene.Expert.index.MergePolicy$MergeException: java.io.IOException: Data > error (cyclic redundancy check) > at > P.Lucene.Expert.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:369) > at > P.Lucene.Expert.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:338) > Caused by: java.io.IOException: Data error (cyclic redundancy check) > at java.io.RandomAccessFile.readBytes(Native Method) > at java.io.RandomAccessFile.read(RandomAccessFile.java:315) > at P.Lucene.Expert.store.FSDirectory$FSIndexInput > > When could be the problem here? > Since it threw the application, the index stayed open. Is there a > possibility to close it properly? to save the data? > > Many thanks, > Liat > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
