Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-29530

.frm was lost after database was not shutdown normally

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.1.14
    • N/A
    • Server
    • None

    Description

      Our server shutdown abnormally after no space left on the device, then after recovery, a certain .frm file was lost and some tables are corrupted.

      2022-08-23 12:00:05 7fbfc83dcf00 InnoDB: Error: Write to file ./new_meeting_master_hanpda/te_groupware_businesstrips.ibd failed at offset 65536.
      2022-08-23 12:00:05 7fbfc83dcf00  InnoDB: Assertion failure in thread 140461674974976 in file fil0fil.cc line 5910
      2022-08-23 12:00:10 139691168835456 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
      2022-08-23 12:00:10 139691168835456 [Note] /home/db/mariadb/bin/mysqld (mysqld 10.1.14-MariaDB) starting as process 8800 ...
      2022-08-23 12:00:11 7f0c627f2780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
      2022-08-23 12:00:11 139691168835456 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2022-08-23 12:00:11 139691168835456 [Note] InnoDB: The InnoDB memory heap is disabled
      2022-08-23 12:00:11 139691168835456 [Note] InnoDB: Mutexes and rw_locks use GCC atom80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
      2022-08-23 12:00:17 139691168835456 [Note] InnoDB: 128 rollback segment(s) are active.
      2022-08-23 12:00:17 139691168835456 [Note] InnoDB: Waiting for purge to start
      2022-08-23 12:00:17 139691168835456 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 1445603599479
      2022-08-23 12:00:17 139689705051904 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2022-08-23 12:00:17 139691168835456 [Note] Plugin 'FEEDBACK' is disabled.
      2022-08-23 12:00:17 139691168835456 [Note] Recovering after a crash using tc.log
      2022-08-23 12:00:17 139691168835456 [Note] Starting crash recovery...
      2022-08-23 12:00:17 139691168835456 [Note] Crash recovery finished.
      2022-08-23 12:00:17 139691168835456 [Note] Server socket created on IP: '0.0.0.0'.
      2022-08-23 12:00:17 139691168714496 [ERROR] mysqld: Error writing file '/home/db/mariadb/data/mariadb.pid' (Errcode: 28 "No space left on device")
      2022-08-23 12:00:17 139691168714496 [ERROR] Can't start server: can't create PID file: No space left on device
      2022-08-23 12:00:18 140375693252480 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
      2022-08-23 12:00:18 140375693252480 [Note] /home/db/mariadb/bin/mysqld (mysqld 10.1.14-MariaDB) starting as process 8931 ...
      2022-08-23 12:00:18 7fabc354d780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: The InnoDB memory heap is disabled
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: Memory barrier is not used
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: Using Linux native AIO
      2022-08-23 12:00:18 140375693252480 [Note] InnoDB: Using SSE crc32 instructions
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Initializing buffer pool, size = 256.0M
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Completed initialization of buffer pool
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Highest supported file format is Barracuda.
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: The log sequence numbers 974895060676 and 974895060676 in ibdata files do not match the log sequence number 1445603599489 in the ib_logfiles!
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Database was not shutdown normally!
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Starting crash recovery.
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Reading tablespace information from the .ibd files...
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Restoring possible half-written data pages
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: from the doublewrite buffer...
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: 128 rollback segment(s) are active.
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB: Waiting for purge to start
      2022-08-23 12:00:19 140375693252480 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 1445603599489
      2022-08-23 12:00:19 140374232241920 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2022-08-23 12:00:19 140375693252480 [Note] Plugin 'FEEDBACK' is disabled.
      2022-08-23 12:00:19 140375693252480 [Note] Recovering after a crash using tc.log
      2022-08-23 12:00:19 140375693252480 [Note] Starting crash recovery...
      2022-08-23 12:00:19 140375693252480 [Note] Crash recovery finished.
      2022-08-23 12:00:20 140375693252480 [Note] Server socket created on IP: '0.0.0.0'.
      2022-08-23 12:00:20 140375693131520 [ERROR] mysqld: Error writing file '/home/db/InnoDB: Error: trying to load index PRIMARY for table new_meeting_master_hanpda/te_groupware_businesstrips
      2022-08-23 12:10:35 139829580807936 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:11:35 139829580533504 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:12:35 139829580533504 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:13:35 139829580259072 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:14:35 139829579984640 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:15:35 139829544644352 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:16:35 139829579984640 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:17:35 139829579710208 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 12:18:35 139829579984640 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm fInnoDB: Error: trying to load index PRIMARY for table new_meeting_master_hanpda/te_groupware_businesstrips
      2022-08-23 13:48:35 139829580807936 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 13:49:35 139829544644352 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 13:50:35 139829579984640 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      2022-08-23 13:51:35 139829579984640 [Warning] InnoDB: Cannot open table new_meeting_master_hanpda/te_groupware_businesstrips from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            johannsky Johann Natividad
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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