Comments - Why its mysqld error occurs during Mariabackup

3 years, 8 months ago Anov Siradj

me when triying to do full backup.

...
2020-08-13  9:13:22 0 [Note] InnoDB: Number of pools: 1
2020-08-13  9:13:22 0 [Warning] InnoDB: Unable to open "./ib_logfile0" to check native AIO read support.
2020-08-13  9:13:22 0 [Warning] InnoDB: Linux Native AIO disabled.
2020-08-13  9:13:22 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2020-08-13  9:13:22 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2020-08-13 09:13:22 0x7f48384077c0  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.14/storage/innobase/fil/fil0fil.cc line 548
InnoDB: Failing assertion: success
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
200813  9:13:22 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
...
 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.