[MDEV-26169] DB Crash Inquire about the cause and recovery method (발생 원인 및 복원 방법 문의) [Aria] Created: 2021-07-17  Updated: 2021-08-18  Resolved: 2021-08-18

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.2.23
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: KANG Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

centos6.8


 Description   

[ERROR] Got error 127 when reading table '~~~ 로그가 기록되면서 Crash가 발생되었습니다.
엔진은 Aria 로 사용중입니다.

해당 오류가 발생되는 원인을 할 수 있을 까요?
mysqlchekc -uroot -p --auto-repair DB명으로 해서 깨진 테이블 복구를 하였으나 일부 데이터가 유실이 되었습니다.

복구시 데이터 유실이 발생할 수 있는지 해서 문의 드립니다.

다른 복구 방법이 있으면 알려주실수 있으실까요?

==========================================
[error] got error 127 when reading table'~~~~ A crash occurred while logging.
The engine is being used as aria.

Can I do the cause of the error?
Recovering a broken table with mysqlchekc -uroot -p --auto-repairdb name was successful, but some data was lost.

I'm inquiring about the possibility of data loss when recovering.

Could you let me know if there is any other way to recover it?

 Comments   
Comment by Daniel Black [ 2021-07-19 ]

HYUNG, thanks for your bug report. Can you include your mariadb error log so we can check if we have fixed this bug in the releases since your version or not.

With the default aria_recover_options including BACKUP there should be a copy saved.

I don't know how to recover data from Aria files.

Given there have been 16 releases of bug fixes (https://mariadb.com/kb/en/release-notes-mariadb-102-series/) in the 10.2 series maybe you could:

  • stop your current instance
  • copy your datadir including the original crashed files
  • move the backup files to where the original files where in the copy
  • start a 10.2.39 instance (maybe using a container) and examine if it has the lost data
  • Run repair repair like before
  • see if the lost data is recovered.
Generated at Thu Feb 08 09:43:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.