| Server IP : 104.21.38.3 / Your IP : 172.69.176.6 Web Server : Apache System : Linux krdc-ubuntu-s-2vcpu-4gb-amd-blr1-01.localdomain 5.15.0-142-generic #152-Ubuntu SMP Mon May 19 10:54:31 UTC 2025 x86_64 User : www ( 1000) PHP Version : 7.4.33 Disable Function : passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /www/server/mysql/src/mysql-test/suite/innodb/t/ |
Upload File : |
# This is the test case for bug#13628249. Make sure that InnoDB starts
# up correctly and is able to shutdown with --innodb-force-recovery >= 3
# after a crash with active user tranactions.
#
# Restarting is not supported in embedded.
--source include/not_embedded.inc
# This test case needs InnoDB.
-- source include/have_innodb.inc
--disable_query_log
call mtr.add_suppression('InnoDB: Failed to find tablespace for table `mysql`\..* in the cache');
call mtr.add_suppression('InnoDB: Failed to find tablespace for table `test`\.`t1` in the cache');
call mtr.add_suppression('InnoDB: Allocated tablespace [0-9]+, old maximum was [0-9]+');
--enable_query_log
--echo # Restart the server in force recovery mode (2)
let $restart_parameters = restart: --innodb-force-recovery=2;
--source include/restart_mysqld.inc
SELECT @@innodb_force_recovery;
--echo # Restart server in normal mode
let $restart_parameters = restart;
--source include/restart_mysqld.inc
SELECT @@innodb_force_recovery;
#
# Create test data.
#
CREATE TABLE t1(c1 INT PRIMARY KEY) ENGINE=InnoDB STATS_PERSISTENT=0;
BEGIN;
INSERT INTO t1 VALUES(1), (2), (3), (4);
# Ensure that the above data is flushed to the InnoDB redo log,
# by committing transactions (which will force a log flush).
connect (con1, localhost, root);
CREATE TABLE t2(c2 INT PRIMARY KEY) ENGINE=InnoDB STATS_PERSISTENT=0;
DROP TABLE t2;
disconnect con1;
connection default;
--echo # Restart the server in force recovery mode (3)
let $restart_parameters = restart: --innodb-force-recovery=3;
--source include/kill_and_restart_mysqld.inc
SELECT @@innodb_force_recovery;
SELECT COUNT(*) IN (0,4) yes FROM t1;
--echo # Restart the server in force recovery mode (5)
let $restart_parameters = restart: --innodb-force-recovery=5;
--source include/restart_mysqld.inc
SELECT @@innodb_force_recovery;
SELECT COUNT(*) IN (0,4) yes FROM t1;
# Restart the server in normal mode now, otherwise the DROP TABLE t1;
# will cause an assertion failure because essentially it is in read-only
# mode. For -innodb-force-recovery >= 3 a transaction is not assigned a
# rollback segment.
--echo # Restart server in normal mode
let $restart_parameters = restart;
--source include/restart_mysqld.inc
SELECT @@innodb_force_recovery;
SELECT COUNT(*) IN (0,4) yes FROM t1;
DROP TABLE t1;