Dear all,
thanks Jernej for the quick reply.
I still have trouble with the mysql under CREAM: I was also to start mysqld in innodb_force_recovery mode, but the mysqldump afterwards seems to run forever (the gzipped output is already 40 GB and still growing also the db files itself are some 100 MB only).
So I think the only option left is to re-start with a fresh db, although the jobs are lost then (most of them are ATLAS pilots, so they wouldn't really care).
Is there any way to just re-configure the database if I dump it now completely (with yaim? maybe call config_cream_db ? )
Best regards,
Torsten
--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<> <>
<> Dr. Torsten Harenberg [log in to unmask] <>
<> Bergische Universitaet <>
<> FB C - Physik Tel.: +49 (0)202 439-3521 <>
<> Gaussstr. 20 Fax : +49 (0)202 439-2811 <>
<> 42097 Wuppertal <>
<> <>
<><><><><><><>< Of course it runs NetBSD http://www.netbsd.org ><>
|