Hi,
On Mon, Jun 30, 2008 at 3:34 PM, mountainbiker
<
mailing.list.traffic@...> wrote:
> have a cron that run every so often and completely copies the /data/
> directory. Therefore, we move the "corrupt" one out of the way and brought
> back last night's copy of the /data/ directory.
It is not a good idea to copy the data directory 'just like that'.
There is a chance that you copy a data set that is still being
written, resulting in a inconsistent data set. That is why we have a
mechanism e.g. for the automatic bacup to block trnasactions for a
small moment.
> Upon attempting to startup.sh--we get the following mesage:
> Scanning journal [===== ] (4%))
> It takes about 6 minutes per 2%, but when it gets to about 26-30% it goes
> back to 0%. This scanning has been going on now for over 4 hours.
Well you talked about a 15 gig .log file? probably that is the case.
Maybe you have a corrupt database (who knows, see exist.log) resulting
that the transaction mechanism fails to work.... (just an educated
guess)
> Does anyone know what might be going on and how to correct the situation?
Since you do not provide information about problems which are neatly
reported in exist.log we can't help you. Please register on the
mailing list as well please.
regards
Dannes
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open
