[MDEV-30100] Assertion `purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()' - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.5.16, 11.2.0, 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
Fix Version/s: 10.6.16, 10.10.7, 10.11.6, 11.0.4, 11.1.3, 11.2.2
Component/s: Storage Engine - InnoDB
Labels:
- rr-profile
Environment:
centos 7.6

Description

The process exits during mysqld execution, and an error occurs after restarting.

lead to:

InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()

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.

220914 18:23:30 [ERROR] mysqld got signal 6 ;

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

data.tar.xz
927 kB
2023-08-03 08:30

Issue Links

causes

MDEV-32103 InnoDB ALTER TABLE is not crash safe

Closed

duplicates

MDEV-30261 mysqld got signal 6 ;

Closed

relates to

MDEV-29401 InnoDB history list length increased in 10.6 compared to 10.5 for the same load

Closed

Activity

Ascending order - Click to sort in descending order

dongjian created issue - 2022-11-26 02:25

dongjian made changes - 2022-11-26 02:25

Field	Original Value	New Value
Description	The process exits during mysqld execution, and an error occurs after restarting. lead to: {code:c++} InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no() 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. 220914 18:23:30 [ERROR] mysqld got signal 6 ;	The process exits during mysqld execution, and an error occurs after restarting. lead to:InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no() 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. 220914 18:23:30 [ERROR] mysqld got signal 6 ; {code:c++}

dongjian made changes - 2022-11-26 02:25

Description

The process exits during mysqld execution, and an error occurs after restarting.

lead to:InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;
{code:c++}

The process exits during mysqld execution, and an error occurs after restarting.

lead to:
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;
{code:c++}

dongjian made changes - 2022-11-26 02:25

Description

The process exits during mysqld execution, and an error occurs after restarting.

lead to:
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;
{code:c++}

The process exits during mysqld execution, and an error occurs after restarting.

lead to:
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;

dongjian made changes - 2022-11-26 02:25

Description

The process exits during mysqld execution, and an error occurs after restarting.

lead to:
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;

The process exits during mysqld execution, and an error occurs after restarting.

lead to: assertion
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;

dongjian made changes - 2022-11-26 02:26

Description

The process exits during mysqld execution, and an error occurs after restarting.

lead to:

{code:c++}
InnoDB: Failing assertion: purge_sys.tail.trx_no <= purge_sys.rseg->last_trx_no()
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.
220914 18:23:30 [ERROR] mysqld got signal 6 ;
{code}

Daniel Black made changes - 2022-12-18 22:09

Link

This issue duplicates ~~MDEV-30261~~ [ ~~MDEV-30261~~ ]

Matthias Leich made changes - 2023-07-28 09:16

Fix Version/s		11.2 [ 28603 ]
Affects Version/s		11.2.0 [ 29033 ]

Marko Mäkelä made changes - 2023-07-28 09:22

Assignee

Marko Mäkelä [ marko ]

Marko Mäkelä made changes - 2023-07-28 09:23

Labels

rr-profile

Marko Mäkelä made changes - 2023-07-28 14:35

Priority

Major [ 3 ]

Critical [ 2 ]

Marko Mäkelä made changes - 2023-08-03 08:30

Attachment

data.tar.xz [ 71323 ]

Marko Mäkelä made changes - 2023-08-03 13:54

Status

Open [ 1 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2023-08-04 08:43

Link

This issue relates to ~~MDEV-29401~~ [ ~~MDEV-29401~~ ]

Marko Mäkelä made changes - 2023-08-04 14:49

Assignee	Marko Mäkelä [ marko ]	Vladislav Lesin [ vlad.lesin ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Marko Mäkelä made changes - 2023-08-10 13:12

Fix Version/s		10.6 [ 24028 ]
Fix Version/s		10.10 [ 27530 ]
Fix Version/s		10.11 [ 27614 ]
Fix Version/s		11.0 [ 28320 ]
Fix Version/s		11.1 [ 28549 ]
Affects Version/s		10.5 [ 23123 ]
Affects Version/s		10.6 [ 24028 ]
Affects Version/s		10.7 [ 24805 ]
Affects Version/s		10.8 [ 26121 ]
Affects Version/s		10.9 [ 26905 ]
Affects Version/s		10.10 [ 27530 ]
Affects Version/s		10.11 [ 27614 ]
Affects Version/s		11.0 [ 28320 ]
Affects Version/s		11.1 [ 28549 ]
Affects Version/s		11.2 [ 28603 ]

Vladislav Lesin made changes - 2023-08-25 10:08

Status

In Review [ 10002 ]

Stalled [ 10000 ]

Marko Mäkelä made changes - 2023-08-25 11:18

issue.field.resolutiondate

2023-08-25 11:18:29.0

2023-08-25 11:18:29.403

Marko Mäkelä made changes - 2023-08-25 11:18

Fix Version/s		10.6.16 [ 29014 ]
Fix Version/s		10.10.7 [ 29018 ]
Fix Version/s		10.11.6 [ 29020 ]
Fix Version/s		11.0.4 [ 29021 ]
Fix Version/s		11.1.3 [ 29023 ]
Fix Version/s		11.2.2 [ 29035 ]
Fix Version/s	10.6 [ 24028 ]
Fix Version/s	10.10 [ 27530 ]
Fix Version/s	10.11 [ 27614 ]
Fix Version/s	11.0 [ 28320 ]
Fix Version/s	11.1 [ 28549 ]
Fix Version/s	11.2 [ 28603 ]
Assignee	Vladislav Lesin [ vlad.lesin ]	Marko Mäkelä [ marko ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Marko Mäkelä made changes - 2023-09-06 12:22

Link

This issue causes ~~MDEV-32103~~ [ ~~MDEV-32103~~ ]

Marko Mäkelä made changes - 2023-09-07 06:26

Link

This issue causes ~~MDEV-32103~~ [ ~~MDEV-32103~~ ]

Marko Mäkelä made changes - 2023-09-07 06:55

Link

This issue causes ~~MDEV-32103~~ [ ~~MDEV-32103~~ ]

People

Assignee:: Marko Mäkelä

Reporter:: dongjian

Votes:: 1 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 2022-11-26 02:25

Updated:: 2023-10-11 10:41

Resolved:: 2023-08-25 11:18

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration