InnoDB: Error: log file ./ib_logfile0 is of different size 5242880 bytes
[root@zhanglin bin]# ./xtrabackup --defaults-file=/etc/my.cnf --backup --log-stream --target-dir=/mysqlbak/xtrabackup/delta
./xtrabackup version 2.2.3 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /usr/local/mysql/data
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
InnoDB: Error: log file ./ib_logfile0 is of different size 5242880 bytes
InnoDB: than specified in the .cnf file 50331648 bytes!
對於使用了預設 my.cnf(一般教程都會教你使用support-files/my-medium.cnf)
如果中間使用了innodb的話,innodb預設的log file大小是56M
解決方法:
1、關閉資料庫,刪除日誌檔案(或者移動到其他目錄,以防MySQL起不來),重新啟動資料庫。
2、如果上面情況後,來時報同樣的錯誤,接下來修改配置檔案將日誌檔案大小設定成備份資料庫的配置大小(比當前要大很多也行)。
修改引數為:
innodb_log_file_size = 1G
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/30936525/viewspace-2016607/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- [ERROR] InnoDB: ibdata1 different size (rounded down to MB)Error
- 如何選擇配置 MySQL innodb_log_file_sizeMySql
- PHP Fatal error: Allowed memory size of 1610612736 bytesPHPError
- MySQL啟動報錯InnoDB: The innodb_system data file './ibdata1' is of a differentMySql
- 帝國cms網站Fatal error: Allowed memory size of … bytes exhausted怎麼辦?網站Error
- gitignore by file size?Git
- Index column size too large. The maximum column size is 767 bytes.Index
- File size 屬性
- 1709 - Index column size too large. The maximum column size is 767 bytes.Index
- [Err] 1709 - Index column size too large. The maximum column size is 767 bytes.Index
- zblog顯示Allowed memory size of 6553652 bytes exhauste
- 測試中出現ERROR StatusLogger No log4j2 configuration fileError
- log file switch
- InnoDB undo log原理
- Zblog unserialize(): Error at offset 2 of 686 bytesError
- MySQL建立表失敗:Index column size too large. The maximum column size is 767 bytesMySqlIndex
- MySQL error log和bin logMySqlError
- MySQL 5.7 到 5.6,出現 Index column size too large. The maximum column size is 767 bytesMySqlIndex
- MySQL innodb_buffer_pool_size 變數MySql變數
- mysql specified key was too long與Index column size too large. The maximum column size is 767 bytes.MySqlIndex
- innodb_flush_log_at_trx_commitMIT
- log file sync等待事件事件
- 【等待事件】log file sync事件
- MySQL資料庫index column size too large. the maximum column size is 767 bytes問題解決MySql資料庫Index
- ubuntu 命令列更改innodb_buffer_pool_sizeUbuntu命令列
- mysql5.7 資料匯入5.6 Index column size too large. The maximum column size is 767 bytes.MySqlIndex
- InnoDB文件筆記(二)—— Redo Log筆記
- InnoDB文件筆記(三)—— Undo Log筆記
- redo log file 最佳化
- ulimit: core file size: cannot modify limit: Operation not permittedMIT
- iis 0x80070032 Cannot read configuration file because it exceeds the maximum file size
- Solaris syntax error: unexpected end of fileError
- InnoDB purge原理--哪些undo log可purge
- How to Dump Redo Log File Information --metalinkORM
- Mysql系統變數中 log_error_services | log_filter_internal; log_sink_internal 和 log_error_verbosity | 2 解釋MySql變數ErrorFilter
- ORA-01144: File size (4224000 blocks) exceeds maximum of 4194303BloC
- MySQL:Innodb:innodb_flush_log_at_trx_commit引數影響的位置MySqlMIT
- Binary XML file line #2: Error inflatingXMLError
- psql: error: could not connect to server: No such file or directorySQLErrorServer