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

InnoDB: Operating system error number 2 in a file operation.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.26, 10.0.29
    • N/A
    • OTHER
    • CentOS 5.8 (VMWare Guest OS)

    Description

      Hi,

      It happened DB crash with this messages.

      2017-07-24 17:40:20 2b358f091940  InnoDB: Operating system error number 2 in a file operation.
      InnoDB: The error means the system cannot find the path specified.
      170724 17:40:20 [ERROR] InnoDB: File /tmp/#sql654b_24aa3_0.ibd: 'open' returned OS error 71. Cannot continue operation
      pure virtual method called
      pure virtual method called
      pure virtual method called
      terminate called without an active exception
      terminate called without an active exception
      terminate called recursively
      170724 17:40:20 [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.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 10.0.29-MariaDB
      key_buffer_size=402653184
      read_buffer_size=2097152
      max_used_connections=211
      max_threads=8194
      thread_count=91
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 84462163 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x2b353bd7e008
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      170724 17:40:23 mysqld_safe Number of processes running now: 0
      170724 17:40:23 mysqld_safe mysqld restarted
      170724 17:40:24 [Note] /MARIA/mariadb/bin/mysqld (mysqld 10.0.29-MariaDB) starting as process 30193 ...
      2017-07-24 17:40:24 2b3670579600 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 a
      nd with the InnoDB's internal memory allocator.
      

      It happened two times for 3 month.
      I don't know why this happened.
      Please help me.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jeony100 JEON YANG BAIK
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.