mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 03:52:35 +01:00
e6b3e38d62
The new option --log-innodb-page-corruption is introduced. When this option is set, backup is not interrupted if innodb corrupted page is detected. Instead it logs all found corrupted pages in innodb_corrupted_pages file in backup directory and finishes with error. For incremental backup corrupted pages are also copied to .delta file, because we can't do LSN check for such pages during backup, innodb_corrupted_pages will also be created in incremental backup directory. During --prepare, corrupted pages list is read from the file just after redo log is applied, and each page from the list is checked if it is allocated in it's tablespace or not. If it is not allocated, then it is zeroed out, flushed to the tablespace and removed from the list. If all pages are removed from the list, then --prepare is finished successfully and innodb_corrupted_pages file is removed from backup directory. Otherwise --prepare is finished with error message and innodb_corrupted_pages contains the list of the pages, which are detected as corrupted during backup, and are allocated in their tablespaces, what means backup directory contains corrupted innodb pages, and backup can not be considered as consistent. For incremental --prepare corrupted pages from .delta files are applied to the base backup, innodb_corrupted_pages is read from both base in incremental directories, and the same action is proceded for corrupted pages list as for full --prepare. innodb_corrupted_pages file is modified or removed only in base directory. If DDL happens during backup, it is also processed at the end of backup to have correct tablespace names in innodb_corrupted_pages.
32 lines
1.1 KiB
C
32 lines
1.1 KiB
C
#pragma once
|
|
#include "my_dbug.h"
|
|
#ifndef DBUG_OFF
|
|
extern char *dbug_mariabackup_get_val(const char *event, const char *key);
|
|
/*
|
|
In debug mode, execute SQL statement that was passed via environment.
|
|
To use this facility, you need to
|
|
|
|
1. Add code DBUG_EXECUTE_MARIABACKUP_EVENT("my_event_name", key););
|
|
to the code. key is usually a table name
|
|
2. Set environment variable my_event_name_$key SQL statement you want to execute
|
|
when event occurs, in DBUG_EXECUTE_IF from above.
|
|
In mtr , you can set environment via 'let' statement (do not use $ as the first char
|
|
for the variable)
|
|
3. start mariabackup with --dbug=+d,debug_mariabackup_events
|
|
*/
|
|
extern void dbug_mariabackup_event(
|
|
const char *event,const char *key);
|
|
#define DBUG_MARIABACKUP_EVENT(A, B) \
|
|
DBUG_EXECUTE_IF("mariabackup_events", \
|
|
dbug_mariabackup_event(A,B););
|
|
#define DBUG_EXECUTE_FOR_KEY(EVENT, KEY, CODE) \
|
|
DBUG_EXECUTE_IF("mariabackup_inject_code", {\
|
|
char *dbug_val = dbug_mariabackup_get_val(EVENT, KEY); \
|
|
if (dbug_val && *dbug_val) CODE \
|
|
})
|
|
#else
|
|
#define DBUG_MARIABACKUP_EVENT(A,B)
|
|
#define DBUG_MARIABACKUP_EVENT_LOCK(A,B)
|
|
#define DBUG_EXECUTE_FOR_KEY(EVENT, KEY, CODE)
|
|
#endif
|
|
|