Debian Codegraph @

mysql-test/suite/innodb/r/log_5_7_8_case2.result

raw
1 # Create an empty data directory...
2 # Unzip 5_7_8_clean.zip to the created directory...
3 # Kill the server
4 ############################################################################################
5 # Case 2: Attempt to start with invalid set of redo log files.
6 # 2A: InnoDB refuses to start if ib_logfile1 was removed
7 # 2B: InnoDB refuses to start if ib_logfile0 was removed
8 # 2C: InnoDB refuses to start if both redo files were removed
9 # NOTE: Ensure there was no attempt to check if redo is empty.
10 ############################################################################################
11 # Hide the ib_logfile1...
12 # Case 2A: Start MySQL...
13 # Verify...
14 Pattern "Only one redo log file found" found
15 Pattern "innodb-unknown-compound-v" not found
16 # Restore the ib_logfile1...
17 ############################################################################################
18 # Hide the ib_logfile0...
19 # Case 2B: Start MySQL...
20 # Verify...
21 Pattern "Missing ib_logfile0 in the directory" found
22 Pattern "innodb-unknown-compound-v" not found
23 # Restore the ib_logfile0...
24 ############################################################################################
25 # Hide both redo log files (ib_logfile0 and ib_logfile1)...
26 # Case 2C: Start MySQL...
27 # Verify...
28 Pattern "Neither found .* subdirectory, nor .* files" found
29 Pattern "innodb-unknown-compound-v" not found
30 # Restore both redo log files (ib_logfile0 and ib_logfile1)...
31 ############################################################################################
32 # Cleanup...
33 # restart