InnoDB ibdata1 corrupted, innodb_force_recover not working
I think I have checked every post in the internet.
Thing is my MySQL (MariaDB) won't come up and after much testing I have seen it is because of the InnoDB files.
I have tried with different innodb_force_recover and also with mysqld_safe, also with online tools and with every tut I have found.
I'm pretty desperate at this point, so any kind of help is welcome.
The log that matters is this one:
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using Linux native AIO
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using SSE crc32 instructions
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Completed initialization of buffer pool
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Highest supported file format is Barracuda.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The log sequence number 1154517884 in ibdata file do not match the log sequence number 1345427345 in the ib_logfiles!
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: Page directory corruption: infimum not pointed to
mysql innodb mariadb recovery corruption
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I think I have checked every post in the internet.
Thing is my MySQL (MariaDB) won't come up and after much testing I have seen it is because of the InnoDB files.
I have tried with different innodb_force_recover and also with mysqld_safe, also with online tools and with every tut I have found.
I'm pretty desperate at this point, so any kind of help is welcome.
The log that matters is this one:
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using Linux native AIO
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using SSE crc32 instructions
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Completed initialization of buffer pool
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Highest supported file format is Barracuda.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The log sequence number 1154517884 in ibdata file do not match the log sequence number 1345427345 in the ib_logfiles!
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: Page directory corruption: infimum not pointed to
mysql innodb mariadb recovery corruption
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
A nicer formatted log message would help. It also appears to be truncated so a more complete log might help. What MariaDB version? What OS/Distribution?
– danblack
Nov 27 '18 at 21:49
add a comment |
I think I have checked every post in the internet.
Thing is my MySQL (MariaDB) won't come up and after much testing I have seen it is because of the InnoDB files.
I have tried with different innodb_force_recover and also with mysqld_safe, also with online tools and with every tut I have found.
I'm pretty desperate at this point, so any kind of help is welcome.
The log that matters is this one:
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using Linux native AIO
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using SSE crc32 instructions
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Completed initialization of buffer pool
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Highest supported file format is Barracuda.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The log sequence number 1154517884 in ibdata file do not match the log sequence number 1345427345 in the ib_logfiles!
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: Page directory corruption: infimum not pointed to
mysql innodb mariadb recovery corruption
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
I think I have checked every post in the internet.
Thing is my MySQL (MariaDB) won't come up and after much testing I have seen it is because of the InnoDB files.
I have tried with different innodb_force_recover and also with mysqld_safe, also with online tools and with every tut I have found.
I'm pretty desperate at this point, so any kind of help is welcome.
The log that matters is this one:
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using Linux native AIO
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Using SSE crc32 instructions
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Completed initialization of buffer pool
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Highest supported file format is Barracuda.
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: The log sequence number 1154517884 in ibdata file do not match the log sequence number 1345427345 in the ib_logfiles!
2018-11-27 15:00:16 140309240685120 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: Page directory corruption: infimum not pointed to
mysql innodb mariadb recovery corruption
mysql innodb mariadb recovery corruption
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
edited Nov 27 '18 at 19:51
MDCCL
6,86331745
6,86331745
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
asked Nov 27 '18 at 15:07
Arnau ECArnau EC
11
11
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 4 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
A nicer formatted log message would help. It also appears to be truncated so a more complete log might help. What MariaDB version? What OS/Distribution?
– danblack
Nov 27 '18 at 21:49
add a comment |
A nicer formatted log message would help. It also appears to be truncated so a more complete log might help. What MariaDB version? What OS/Distribution?
– danblack
Nov 27 '18 at 21:49
A nicer formatted log message would help. It also appears to be truncated so a more complete log might help. What MariaDB version? What OS/Distribution?
– danblack
Nov 27 '18 at 21:49
A nicer formatted log message would help. It also appears to be truncated so a more complete log might help. What MariaDB version? What OS/Distribution?
– danblack
Nov 27 '18 at 21:49
add a comment |
1 Answer
1
active
oldest
votes
MDEV-13939 Page directory corruption: infimum not pointed appears to be a bug upstream that has some tips on recovery.
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f223556%2finnodb-ibdata1-corrupted-innodb-force-recover-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
MDEV-13939 Page directory corruption: infimum not pointed appears to be a bug upstream that has some tips on recovery.
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
add a comment |
MDEV-13939 Page directory corruption: infimum not pointed appears to be a bug upstream that has some tips on recovery.
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
add a comment |
MDEV-13939 Page directory corruption: infimum not pointed appears to be a bug upstream that has some tips on recovery.
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
MDEV-13939 Page directory corruption: infimum not pointed appears to be a bug upstream that has some tips on recovery.
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
answered Nov 27 '18 at 21:48
danblackdanblack
2,1061214
2,1061214
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f223556%2finnodb-ibdata1-corrupted-innodb-force-recover-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
A nicer formatted log message would help. It also appears to be truncated so a more complete log might help. What MariaDB version? What OS/Distribution?
– danblack
Nov 27 '18 at 21:49