Skip to content

M
MariaDB
Commit d98567c4 authored by osku@127.(none)'s avatar osku@127.(none)
Browse files
Options

InnoDB: Print better error message when log files are missing/corrupt 

(bug #13497).
parent acdc193a
Show whitespace changes
Inline Side-by-side
Showing with 3 additions and 1 deletion
innobase/buf/buf0buf.c
View file @ d98567c4
...@@ -321,7 +321,9 @@ buf_page_is_corrupted( ...@@ -321,7 +321,9 @@ buf_page_is_corrupted(
fprintf(stderr, fprintf(stderr,
" InnoDB: Error: page %lu log sequence number %lu %lu\n" " InnoDB: Error: page %lu log sequence number %lu %lu\n"
"InnoDB: is in the future! Current system log sequence number %lu %lu.\n" "InnoDB: is in the future! Current system log sequence number %lu %lu.\n"
"InnoDB: Your database may be corrupt.\n", "InnoDB: Your database may be corrupt or you may have copied the InnoDB\n"
"InnoDB: tablespace but not the InnoDB log files. See\n"
"http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.\n",
(ulong) mach_read_from_4(read_buf + FIL_PAGE_OFFSET), (ulong) mach_read_from_4(read_buf + FIL_PAGE_OFFSET),
(ulong) ut_dulint_get_high( (ulong) ut_dulint_get_high(
mach_read_from_8(read_buf + FIL_PAGE_LSN)), mach_read_from_8(read_buf + FIL_PAGE_LSN)),
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7