Re: ERROR: could not read any segments file in directory

Mike, Just out of curiosity, how to find the number of commits to index?. do you have any links to read about this?. Thanks, Prakash On Mon, Jul 29, 2013 at 4:25 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > On Mon, Jul 29, 2013 at 5:03 AM, Prakash Chinnakannan > wrote: > > Tha

Re: ERROR: could not read any segments file in directory

On Mon, Jul 29, 2013 at 5:03 AM, Prakash Chinnakannan wrote: > Thanks Mike, we'd restored the index content from the backup. I will also > suggest to move the index to local storage. OK, good that you have backups. >> Do you commit frequently and has this index been running for a very, very > l

Re: ERROR: could not read any segments file in directory

Thanks Mike, we'd restored the index content from the backup. I will also suggest to move the index to local storage. > Do you commit frequently and has this index been running for a very, very long time? Yes, index files would be there for more than 3 yrs and frequent add/update and delete oper

Re: ERROR: could not read any segments file in directory

OK, you have only one segments file, and it sounds like it was corrupted by the crash of your SAN. I don't think there's much you can do but re-index. Maybe move your index to local storage: it sounds like this SAN is not to be trusted. Separately, your segment numbers are truly immense. Do you

Re: ERROR: could not read any segments file in directory

Thanks for your time Mike, Yes the commit has been made successfully before crashing. Here is the output of ls -lrt on searchIndex/ directory >> searchIndex#] ls -lrt total 50624356 -rw-r--r-- 1 root root 32991 Jul 26 06:42 _18vyk7.fnm -rw-r--r-- 1 root root 39608652 Jul 26 06:42 _18vyk7.fdx -r

Re: ERROR: could not read any segments file in directory

Thanks for your time Mike, Yes the commit has been made successfully before crashing. Here is the output of ls -lrt on searchIndex/ directory >> searchIndex#] ls -lrt total 50624356 -rw-r--r-- 1 root root 32991 Jul 26 06:42 _18vyk7.fnm -rw-r--r-- 1 root root 39608652 Jul 26 06:42 _18vyk7.fdx -r

Re: ERROR: could not read any segments file in directory

Likely there's nothing easy you can do to recover the index. If the crash was merely an "outage", and the IO system did not flip bits on files that were committed, then the index should have been intact. Can you post the ls -l of the index directory? Had you successfully committed to this index