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

OS Error 201 appears in MariaDB log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 10.2.7
    • Fix Version/s: N/A
    • Component/s: Server
    • Labels:
      None
    • Environment:
      Windows 2008 R1 (32bit) running as VM on ESXi 6.0 hypervisor.

      Description

      Migrated from MariaDB to 10.1.26 to 10.2.7 on one of our Windows 2008 R1 (32bit) platforms.
      we see a number of errors logged in the mariaDB log file.
      Functionality wise; all seems fine.

      There are two types of errors logged
      1) Problem
      2017-08-17 7:10:13 5064 [ERROR] InnoDB: Operating system error number 1 in a file operation.
      2017-08-17 7:10:13 5064 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
      2017-08-17 7:10:13 5064 [ERROR] InnoDB: File \\.\D:: 'DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY)' returned OS error 201.

      2) when clients connect from MySQL workbench and disconnect cleanly; and also when I connect with Hibernate through our application; get following logged
      2017-08-17 7:16:53 3944 [Warning] Aborted connection 18 to db: 'datafactorydb' user: 'rjis' host: '127.0.0.1' (Got an error reading communication packets)
      2017-08-17 7:17:07 3944 [Warning] Aborted connection 19 to db: '*****' user: '**' host: '127.0.0.1' (Got an error reading communication packet.

      both problems do not seem to break anything; the DB seems to function fine.

      As soon as I go back to 10.1.26; all is ok; there is no network or hardware issues; these problems only appear when on version 10.2.*

      These problems appear also with 10.2.5 and 10.2.6;
      I also get this problem on all my other Windows 2008 R1 32bit servers I have tried to migrate to 10.2 on; even with a fresh install.

      Is this a bug; is it because INNODB is running version 5.7.18 and not 5.7.19?

      My my.ini is pretty standard; no major changes from the default for a server configuration.

      Any ideas \ help please?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              wlad Vladislav Vaintroub
              Reporter:
              slaterss Stuart Slater
              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.