11.10.2012 03:25, Andriy Podanenko пишет:
http://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html
Запускать, повышая число, пока не стартанет, потом сделать бекап, и
пересобрать базу
2012/10/10 greenh <[email protected] <mailto:[email protected]>>
Доброй вечер
Господа, подскажите плз
имеется 80гиговая mysql база
после переноса на другой тазик она стала периодически ( раз в 2-3
часа) выдавать вот такое
121010 23:22:50 mysqld_safe mysqld restarted
121010 23:22:51 [Note] Plugin 'FEDERATED' is disabled.
121010 23:22:52 InnoDB: Initializing buffer pool, size = 12.0G
121010 23:22:53 InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 426 2507657517
<tel:2507657517>
121010 23:22:53 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...
InnoDB: Doing recovery: scanned up to log sequence number 426
2512900096 <tel:2512900096>
InnoDB: Doing recovery: scanned up to log sequence number 426
2518142976 <tel:2518142976>
InnoDB: Doing recovery: scanned up to log sequence number 426
2523385856 <tel:2523385856>
InnoDB: Doing recovery: scanned up to log sequence number 426
2528628736 <tel:2528628736>
InnoDB: Doing recovery: scanned up to log sequence number 426
2533871616 <tel:2533871616>
InnoDB: Doing recovery: scanned up to log sequence number 426
2539114496 <tel:2539114496>
InnoDB: Doing recovery: scanned up to log sequence number 426
2575814656
InnoDB: Doing recovery: scanned up to log sequence number 426
2581057536
.............................................
nnoDB: Doing recovery: scanned up to log sequence number 426
2885144576
InnoDB: Doing recovery: scanned up to log sequence number 426
2886661501
121010 23:23:39 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 <tel:41%2042%2043%2044%2045>
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: Last MySQL binlog file position 0 188749931, file name
./mysql-bin.000006
121010 23:29:32 InnoDB: Started; log sequence number 426 2886661501
121010 23:29:32 [Note] Recovering after a crash using mysql-bin
121010 23:29:33 [Note] Starting crash recovery...
121010 23:29:33 [Note] Crash recovery finished.
121010 23:29:33 [Note] Event Scheduler: Loaded 0 events
121010 23:29:33 [Note] /usr/local/libexec/mysqld: ready for
connections.
Version: '5.1.65-log' socket: '/tmp/mysql.sock' port: 3306
FreeBSD port: mysql-server-5.1.65
Подскажите плз, что это может быть и куда смотреть?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
