> I'm currently running some checks on the raid itself to see > if the problem lies there, I just wanted to make sure we > weren't tickling a bug that was fixed in a later version of > MaxDB - I don't want to spend my time hunting for a cause > only to find out the cause is known, and it's long since been > corrected. :)
You're running 7.5.0 Build 008? This is a very old release, you should consider to upgrade to a newer release :-) Check dmesg, maybe there's some information on what went wrong. -- SIEGENIA-AUBI KG Informationswesen i.A. Markus D�hr SAP-CC/BC, SAPDB-DBA Tel.: +49 6503 917-152 Fax: +49 6503 917-7152 E-Mail: [EMAIL PROTECTED] Internet: http://www.siegenia-aubi.com -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
