[vz-users] mysql startet nicht mehr

[G. Stenzel]

Hallo Liste

Ich verwende das vorletzte VZ-Image auf einem Raspi. Während meines
Urlaubs gab es im Ort eine Stromabschaltung. Auf dem Raspi startet nun
der mysql-Server nicht mehr, vermutlich aus diesem Grund.

Nach einem Reboot stehen folgende Zeilen im syslog:

Sep  6 22:36:25 raspiname mysqld: 130906 22:36:25 InnoDB: 5.5.31
started; log sequence number 43307707
Sep  6 22:36:25 raspiname mysqld: 130906 22:36:25  InnoDB: Assertion
failure in thread 2784679008 in file fut0lst.ic line 83
Sep  6 22:36:25 raspiname mysqld: InnoDB: Failing assertion: addr.page
== FIL_NULL || addr.boffset >= FIL_PAGE_DATA
Sep  6 22:36:25 raspiname mysqld: InnoDB: We intentionally generate a
memory trap.
Sep  6 22:36:25 raspiname mysqld: InnoDB: Submit a detailed bug report
to http://bugs.mysql.com.
Sep  6 22:36:25 raspiname mysqld: InnoDB: If you get repeated
assertion failures or crashes, even
Sep  6 22:36:25 raspiname mysqld: InnoDB: immediately after the mysqld
startup, there may be
Sep  6 22:36:25 raspiname mysqld: InnoDB: corruption in the InnoDB
tablespace. Please refer to
Sep  6 22:36:25 raspiname mysqld: InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
Sep  6 22:36:25 raspiname mysqld: InnoDB: about forcing recovery.
Sep  6 22:36:25 raspiname mysqld: 20:36:25 UTC - mysqld got signal 6 ;
Sep  6 22:36:25 raspiname mysqld: This could be because you hit a bug.
It is also possible that this binary
Sep  6 22:36:25 raspiname mysqld: or one of the libraries it was
linked against is corrupt, improperly built,
Sep  6 22:36:25 raspiname mysqld: or misconfigured. This error can
also be caused by malfunctioning hardware.
Sep  6 22:36:25 raspiname mysqld: We will try our best to scrape up
some info that will hopefully help
Sep  6 22:36:25 raspiname mysqld: diagnose the problem, but since we
have already crashed, 
Sep  6 22:36:25 raspiname mysqld: something is definitely wrong and
this may fail.
Sep  6 22:36:25 raspiname mysqld: 
Sep  6 22:36:25 raspiname mysqld: key_buffer_size=16777216
Sep  6 22:36:25 raspiname mysqld: read_buffer_size=131072
Sep  6 22:36:25 raspiname mysqld: max_used_connections=0
Sep  6 22:36:25 raspiname mysqld: max_threads=151
Sep  6 22:36:25 raspiname mysqld: thread_count=0
Sep  6 22:36:25 raspiname mysqld: connection_count=0
Sep  6 22:36:25 raspiname mysqld: It is possible that mysqld could use
up to 
Sep  6 22:36:25 raspiname mysqld: key_buffer_size + (read_buffer_size
+ sort_buffer_size)*max_threads = 346080 K  bytes of memory
Sep  6 22:36:25 raspiname mysqld: Hope that's ok; if not, decrease
some variables in the equation.
Sep  6 22:36:25 raspiname mysqld: 
Sep  6 22:36:25 raspiname mysqld: Thread pointer: 0x0
Sep  6 22:36:25 raspiname mysqld: Attempting backtrace. You can use
the following information to find out
Sep  6 22:36:25 raspiname mysqld: where mysqld died. If you see no
messages after this, something went
Sep  6 22:36:25 raspiname mysqld: terribly wrong...
Sep  6 22:36:25 raspiname mysqld: stack_bottom = 0 thread_stack
0x30000
Sep  6 22:36:25 raspiname mysqld: The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html contains
Sep  6 22:36:25 raspiname mysqld: information that should help you
find out what is causing the crash.
Sep  6 22:36:25 raspiname mysqld_safe: mysqld from pid file
/var/run/mysqld/mysqld.pid ended


Wenn ich mysql in der Konsole starte, erhalte ich folgende Meldung:

pi at raspiname:/var/lib$ /etc/init.d/mysql start
df: `/var/lib/mysql/.': Permission denied
df: no file systems processed
[....] /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is
too full! [FA failed!

Ein 'df -h' gibt folgendes aus:

Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
rootfs           15G    2,3G   12G   17% /
/dev/root        15G    2,3G   12G   17% /
devtmpfs        235M       0  235M    0% /dev
tmpfs            49M    396K   49M    1% /run
tmpfs           5,0M       0  5,0M    0% /run/lock
tmpfs            98M       0   98M    0% /run/shm
/dev/mmcblk0p1   56M     19M   38M   33% /boot
tmpfs           243M    8,0K  243M    1% /tmp
/dev/root        15G    2,3G   12G   17% /var/log.hdd
ramlog-tmpfs     30M    6,3M   24M   21% /var/log

Ein Speicherplatzproblem scheint es demnach kaum zu geben. Hat es
eventuell die Datenbank zerschossen?
Kann mir bitte jemand Hinweise geben, das Problem einzukreisen und den
Server wieder zu starten?

Viele Grüße