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

Got lots of Compression failed for space: xxxx

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.2
    • N/A
    • None
    • CentOS 7.x x86_64

    Description

      2017-09-29  9:05:29 140321115916032 [Warning] InnoDB: Compression failed for space: 2390 name: mydb/t1 len: 16384 err: 0 write_size: 0 compression method: LZMA.
      2017-09-29  9:05:30 140321132701440 [Warning] InnoDB: Compression failed for space: 2372 name: mydb/t2 len: 16384 err: 0 write_size: 0 compression method: LZMA.
      2017-09-29  9:05:31 140321124308736 [Warning] InnoDB: Compression failed for space: 2382 name: mydb/t3 len: 16384 err: 0 write_size: 0 compression method: LZMA.
      2017-09-29  9:05:37 140321090737920 [Warning] InnoDB: Compression failed for space: 2446 name: mydb/t4 len: 16384 err: 0 write_size: 0 compression method: LZMA.
      2017-09-29  9:05:38 140321115916032 [Warning] InnoDB: Compression failed for space: 2437 name: mydb/t5 len: 16384 err: 0 write_size: 0 compression method: LZMA.
      2017-09-29  9:06:08 140321132701440 [Warning] InnoDB: Compression failed for space: 2284 name: mydb/t6 len: 16384 err: 0 write_size: 0 compression method: LZMA.
      

      What does it mean, how can I fix these warning messages? Thanks.

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            mxu Michael Xu
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.