So, did this happen because he copied the data while in an inconsistent
state? I'm a bit surprised that an inconsistent index is ever left on
disk (except for temporarily while something is being written). Would
this happen if there was a Writer that was not closed?
On Apr 8, 2005, at 1:22 PM, Daniel Naber wrote:
On Friday 08 April 2005 19:26, Bill Tschumy wrote:
The only thought I had was that he copied the data while the app was
still running and perhaps it was in an inconsistent state.
Yes, the *.cfs shows that this is a compound index which has *.fnm
files
only when it's being modified. You're not asking how to fix the index,
but
that might be possible by modifying the segments file.
Regards
Daniel
--
http://www.danielnaber.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Bill Tschumy
Otherwise -- Austin, TX
http://www.otherwise.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
