InnoDB: Error: the OS said file flush did not succeed

いつの間にか mysql が落ちていた。そしてまだ立ち上がらない。

081111  1:56:26  InnoDB: Error: the OS said file flush did not succeed
081111  1:56:27  InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: File operation call: 'flush'.
InnoDB: Cannot continue operation.

Number of processes running now: 0
081111 01:56:29  mysqld restarted
081111  1:56:30  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
081111  1:56:31  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 7 2108323381.
InnoDB: Doing recovery: scanned up to log sequence number 7 2108364559
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 63 row operations to undo
InnoDB: Trx id counter is 0 10543104
081111  1:56:31  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 
77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 144, file name mysqld-bin.000020
InnoDB: Starting in background the rollback of uncommitted transactions
081111  1:56:32  InnoDB: Rolling back trx with id 0 10542683, 63 rows to undo
081111  1:56:33  InnoDB: Started; log sequence number 7 2108364559
081111  1:56:37 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=/var/run/mysqld/mysqld-relay-bin' to avoid this probl
em.

InnoDB: Rolling back of trx id 0 10542683 completed
081111  1:56:37  InnoDB: Rollback of non-prepared transactions completed
081111  1:56:37 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
081111  1:56:37 [Note] Slave I/O thread: connected to master 'repl@192.168.1.1:3306',  replication started in log 'mysqld-bin.000020' at position 1058192307
081111  1:56:37 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000020' at position 1058178872, relay log '/var/run/mysqld/mysqld-relay-bin.000230' position: 16306827
081111  2:37:28  InnoDB: Error: the OS said file flush did not succeed
081111  2:37:28  InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: File operation call: 'flush'.
InnoDB: Cannot continue operation.

はじめて見るログです。読んだ感想としては「イヤな感じ」がしますよね。
何が原因なのかわからないし、ぶっちゃけちゃうとわからなくてもいいかなぁ、なんて思ってます。
落ちたのがスレーブ側なのでもう一回スレーブ組み直してもいいなぁと。
ただ、ひとつだけ大きな DB があって約5,000万レコード。マスタからこのデータ持ってくるの面倒。
週末にでもやってみましょうかね。

その5,000万レコードの DB は Catalyst + DBIC で作ったアプリの DB なんですけど、この量のレコードでも結構普通に動くものです。DBIC で sth 直接握って SQL 発行したりしなくても大丈夫。
ま、僕くらいしか使ってないからね。

それはそうと、MT の「公開状態」の設定がデフォルトで「公開」になっていたんですけど、誰ですかいじったのは？誰にも言いませんのでコメントください。