- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我安装了 strator 服务器的完整备份,并且必须在 my.cnf 中使用“innodb_force_recovery=1”才能启动我的数据库。
但是,我无法写入/更改数据库/表,并要求取消注释“innodb_force_recovery=1”选项。
注释掉后,我无法启动 SQL Server。任何帮助将不胜感激。我得到以下堆栈跟踪:
从 innodb_force_recovery=1 开始
160108 3:28:04 [Note] Event Scheduler: Loaded 0 events
160108 3:28:04 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.38-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
160108 3:28:21 [Note] /usr/sbin/mysqld: Normal shutdown
160108 3:28:21 [Note] Event Scheduler: Purging the queue. 0 events
160108 3:28:21 InnoDB: Starting shutdown...
160108 3:28:23 InnoDB: Shutdown completed; log sequence number 946126358
160108 3:28:23 [Note] /usr/sbin/mysqld: Shutdown complete
160108 3:28:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160108 3:28:41 [Note] Plugin 'FEDERATED' is disabled.
160108 3:28:41 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
160108 3:28:41 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
160108 3:28:41 InnoDB: The InnoDB memory heap is disabled
160108 3:28:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160108 3:28:41 InnoDB: Compressed tables use zlib 1.2.8
160108 3:28:41 InnoDB: Using Linux native AIO
160108 3:28:41 InnoDB: Initializing buffer pool, size = 5.0M
160108 3:28:41 InnoDB: Completed initialization of buffer pool
160108 3:28:41 InnoDB: highest supported file format is Barracuda.
160108 3:28:41 InnoDB: Waiting for the background threads to start
160108 3:28:42 InnoDB: Error: tablespace size stored in header is 4224 pages, but
160108 3:28:42 InnoDB: the sum of data file sizes is only 3840 pages
160108 3:28:42 InnoDB: 5.5.38 started; log sequence number 946126358
160108 3:28:42 InnoDB: !!! innodb_force_recovery is set to 1 !!!
160108 3:28:42 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160108 3:28:42 [Note] - '0.0.0.0' resolves to '0.0.0.0';
160108 3:28:42 [Note] Server socket created on IP: '0.0.0.0'.
160108 3:28:42 [Note] Event Scheduler: Loaded 0 events
160108 3:28:42 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.38-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
在没有 innodb_force_recovery=1 的情况下重新启动
160108 3:29:28 [Note] /usr/sbin/mysqld: Normal shutdown
160108 3:29:28 [Note] Event Scheduler: Purging the queue. 0 events
160108 3:29:28 InnoDB: Starting shutdown...
160108 3:29:29 InnoDB: Shutdown completed; log sequence number 946126358
160108 3:29:29 [Note] /usr/sbin/mysqld: Shutdown complete
160108 3:29:29 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160108 3:29:29 [Note] Plugin 'FEDERATED' is disabled.
160108 3:29:29 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
160108 3:29:29 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
160108 3:29:29 InnoDB: The InnoDB memory heap is disabled
160108 3:29:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160108 3:29:29 InnoDB: Compressed tables use zlib 1.2.8
160108 3:29:29 InnoDB: Using Linux native AIO
160108 3:29:29 InnoDB: Initializing buffer pool, size = 5.0M
160108 3:29:29 InnoDB: Completed initialization of buffer pool
160108 3:29:29 InnoDB: highest supported file format is Barracuda.
160108 3:29:30 InnoDB: Waiting for the background threads to start
160108 3:29:31 InnoDB: Error: tablespace size stored in header is 4224 pages, but
160108 3:29:31 InnoDB: the sum of data file sizes is only 3840 pages
160108 3:29:31 InnoDB: Cannot start InnoDB. The tail of the system tablespace is
160108 3:29:31 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
160108 3:29:31 InnoDB: inappropriate way, removing ibdata files from there?
160108 3:29:31 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
160108 3:29:31 InnoDB: a startup if you are trying to recover a badly corrupt database.
160108 3:29:31 [ERROR] Plugin 'InnoDB' init function returned error.
160108 3:29:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160108 3:29:31 [ERROR] Unknown/unsupported storage engine: InnoDB
160108 3:29:31 [ERROR] Aborting
160108 3:29:31 [Note] /usr/sbin/mysqld: Shutdown complete
160108 3:29:32 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160108 3:29:32 [Note] Plugin 'FEDERATED' is disabled.
160108 3:29:32 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
160108 3:29:32 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
160108 3:29:32 InnoDB: The InnoDB memory heap is disabled
160108 3:29:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160108 3:29:32 InnoDB: Compressed tables use zlib 1.2.8
160108 3:29:32 InnoDB: Using Linux native AIO
160108 3:29:32 InnoDB: Initializing buffer pool, size = 5.0M
160108 3:29:32 InnoDB: Completed initialization of buffer pool
160108 3:29:32 InnoDB: highest supported file format is Barracuda.
160108 3:29:32 InnoDB: Waiting for the background threads to start
160108 3:29:33 InnoDB: Error: tablespace size stored in header is 4224 pages, but
160108 3:29:33 InnoDB: the sum of data file sizes is only 3840 pages
160108 3:29:33 InnoDB: Cannot start InnoDB. The tail of the system tablespace is
160108 3:29:33 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
160108 3:29:33 InnoDB: inappropriate way, removing ibdata files from there?
160108 3:29:33 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
160108 3:29:33 InnoDB: a startup if you are trying to recover a badly corrupt database.
160108 3:29:33 [ERROR] Plugin 'InnoDB' init function returned error.
160108 3:29:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160108 3:29:33 [ERROR] Unknown/unsupported storage engine: InnoDB
160108 3:29:33 [ERROR] Aborting
160108 3:29:33 [Note] /usr/sbin/mysqld: Shutdown complete
160108 3:29:34 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160108 3:29:34 [Note] Plugin 'FEDERATED' is disabled.
160108 3:29:34 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
160108 3:29:34 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
160108 3:29:34 InnoDB: The InnoDB memory heap is disabled
160108 3:29:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160108 3:29:34 InnoDB: Compressed tables use zlib 1.2.8
160108 3:29:34 InnoDB: Using Linux native AIO
160108 3:29:34 InnoDB: Initializing buffer pool, size = 5.0M
160108 3:29:34 InnoDB: Completed initialization of buffer pool
160108 3:29:34 InnoDB: highest supported file format is Barracuda.
160108 3:29:34 InnoDB: Waiting for the background threads to start
160108 3:29:35 InnoDB: Error: tablespace size stored in header is 4224 pages, but
160108 3:29:35 InnoDB: the sum of data file sizes is only 3840 pages
160108 3:29:35 InnoDB: Cannot start InnoDB. The tail of the system tablespace is
160108 3:29:35 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
160108 3:29:35 InnoDB: inappropriate way, removing ibdata files from there?
160108 3:29:35 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
160108 3:29:35 InnoDB: a startup if you are trying to recover a badly corrupt database.
160108 3:29:35 [ERROR] Plugin 'InnoDB' init function returned error.
160108 3:29:35 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160108 3:29:35 [ERROR] Unknown/unsupported storage engine: InnoDB
160108 3:29:35 [ERROR] Aborting
160108 3:29:35 [Note] /usr/sbin/mysqld: Shutdown complete
最佳答案
innodb_force_recovery
的目的是以只读模式启动MySQL并抢救用户数据。在极少数情况下,它可以用于修复表空间(例如,删除损坏的索引),但这是一个异常(exception)。
当您进行转储时,您应该停止 MySQL,将现有 MySQL 文件移动到存档并从转储中重新创建数据库。
# service mysql stop
# sed -i 's/innodb_force_recovery=[1-6]/innodb_force_recovery=0' /etc/my.cnf
# mv /var/lib/mysql /var/lib/mysql.archive
# mkdir /var/lib/mysql
# chown -R mysql:mysql /var/lib/mysql
# service mysql start
# mysql < dump.sql
关于mysql - innodb恢复后如何重启mysql,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/34668583/
目前我正在构建相当大的网络系统,我需要强大的 SQL 数据库解决方案。我选择 Mysql 而不是 Postgres,因为一些任务需要只读(MyISAM 引擎)而其他任务需要大量写入(InnoDB)。
我在 mysql 中使用如下命令。当它显示表格数据时,它被格式化为一个非常干净的表格,间距均匀且 |作为列分隔符。 SELECT * FROM TABLE_NAME; 当我从 CLI 运行命令时,如下
我知道这个问题之前已经被问过好几次了,我已经解决了很多问题,但到目前为止没有任何效果。 MySQL 试图将自身安装到的目录 (usr/local/mysql) 肯定有问题。关于我的错误的奇怪之处在于我
以下是我的 SQL 数据结构,我正在尝试如下两个查询: Select Wrk_ID, Wrk_LastName, Skill_Desc from Worker, Skill where
我们有一个本地 mysql 服务器(不在公共(public)域上),并希望将该服务器复制到我们拥有的 google 云 sql 实例。我的问题是:1.这可能吗?2.我们的本地服务器只能在本地网络上访问
我有一个表(test_table),其中一些字段值(例如字段 A、B 和 C)是从外部应用程序插入的,还有一个字段(字段 D),我想从现有表(store_table)插入其值,但在插入前者(A、B 和
我想创建一个 AWS RDS 实例,然后使用 terraform 管理数据库用户。因此,首先,我创建了一个 RDS 实例,然后使用创建的 RDS 实例初始化 mysql 提供程序,以进一步将其用于用户
当用户在我的网站上注册时,他们会在我的一个数据库中创建自己的表格。该表存储用户发布的所有帖子。我还想做的是也为他们生成自己的 MySql 用户——该用户仅有权从他们的表中读取、写入和删除。 创建它应该
我有一个关于 ColdFusion 和 Mysql 的问题。我有两个表:PRODUCT 和 PRODUCT_CAT。我想列出包含一些标记为:IS_EXTRANET=1 的特殊产品的类别。所以我写了这个
我想获取 recipes_id 列的值,以获取包含 ingredient_id 的 2,17 和 26 条目的值。 假设 ingredient_id 2 丢失则不获取记录。 我已经尝试过 IN 运算符
在 Ubuntu 中,我通常安装两者,但 MySQL 的客户端和服务器之间有什么区别。 作为奖励,当一个新语句提到它需要 MySQL 5.x 时,它是指客户端、服务器还是两者兼而有之。例如这个链接ht
我重新访问了我的数据库并注意到我有一些 INT 类型的主键。 这还不够独特,所以我想我会有一个指导。 我来自微软 sql 背景,在 ssms 中你可以 选择类型为“uniqeidentifier”并自
我的系统上有 MySQL,我正在尝试确定它是 Oracle MySQL 还是 MySQL。 Oracle MySQL 有区别吗: http://www.oracle.com/us/products/m
我是在生产 MySQL 中运行的应用程序的新维护者。之前的维护者已经离开,留下的文档很少,而且联系不上了。 我面临的问题是执行以下请求大约需要 10 秒: SELECT COUNT(*) FROM `
我有两个位于不同机器上的 MySQL 数据库。我想自动将数据从一台服务器传输到另一台服务器。比方说,我希望每天早上 4:00 进行数据传输。 可以吗?是否有任何 MySQL 内置功能可以让我们做到这一
有什么方法可以使用 jdbc 查询位于 mysql 根目录之外的目录中的 mysql 表,还是必须将它们移动到 mysql 根目录内的数据库文件夹中?我在 Google 上搜索时没有找到任何东西。 最
我在 mysql 数据库中有两个表。成员和 ClassNumbers。两个表都有一个付费年份字段,都有一个代码字段。我想用代码数字表中的值更新成员表中的付费年份,其中成员中的代码与 ClassNumb
情况:我有 2 台服务器,其中一台当前托管一个实时 WordPress 站点,我希望能够将该站点转移到另一台服务器,以防第一台服务器出现故障。传输源文件很容易;传输数据库是我需要弄清楚如何做的。两台服
Phpmyadmin 有一个功能是“复制数据库到”..有没有mysql查询来写这个函数?类似于将 db A 复制到新的 db B。 最佳答案 首先创建复制数据库: CREATE DATABASE du
我有一个使用 mySQL 作为后端的库存软件。我已经在我的计算机上对其进行了测试,并且运行良好。 当我在计算机上安装我的软件时,我必须执行以下步骤: 安装 mySQL 服务器 将用户名指定为“root
我是一名优秀的程序员,十分优秀!