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

ERROR in log file: IOCTL_STORAGE_QUERY_PROPERTY

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 10.2.4, 10.2.5, 10.3.0, 10.2.6
    • 10.2.9
    • Storage Engine - InnoDB
    • None
    • win7 x64, 32GB RAM, SSD, Mariadb 10.2.6 x64 version

    Description

      When importing a database using a previous dump, The following errors appear in the error log. The sequence of three lines seem to appear once per table created. I can find no helpful reference to any of the statements.
      The tables are created ok, and populated with data. I have tried this multiple times, with multiple databases, also a single table manually - in each case the result is the same:

      2017-05-29 16:41:03 1092 [ERROR] InnoDB: Operating system error number 1 in a file operation.
      2017-05-29 16:41:03 1092 [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-05-29 16:41:03 1092 [ERROR] InnoDB: File \\.\d:: 'DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY)' returned OS error 201.

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11254 innodb-use-trim has no effect in 10.2

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13558 OS Error 201 appears in MariaDB log

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

            The call DeviceIoControl(handle, IOCTL_STORAGE_QUERY_PROPERTY, …) was originally added in MDEV-11254, in this commit.
            One problem in the patch was fixed 2 days later.

            Both changes were first released in MariaDB 10.2.4.

            According to this MSDN article, the "Operating system error 1" could be ERROR_INVALID_FUNCTION.

            marko Marko Mäkelä added a comment - The call DeviceIoControl(handle, IOCTL_STORAGE_QUERY_PROPERTY, …) was originally added in MDEV-11254 , in this commit . One problem in the patch was fixed 2 days later . Both changes were first released in MariaDB 10.2.4. According to this MSDN article , the "Operating system error 1" could be ERROR_INVALID_FUNCTION.
            jplindst Jan Lindström (Inactive) added a comment -

            wlad This seems to be Windows problem and both patches mentioned above are by you.

            jplindst Jan Lindström (Inactive) added a comment - wlad This seems to be Windows problem and both patches mentioned above are by you.
            Sergey_W Sergii Volikov added a comment - - edited

            A similar situation for Windows Server 2008 R2

            Sergey_W Sergii Volikov added a comment - - edited A similar situation for Windows Server 2008 R2
            Sergey_W Sergii Volikov added a comment -

            Vladislav Vaintroub, thank you!

            Sergey_W Sergii Volikov added a comment - Vladislav Vaintroub, thank you!
            Sergey_W Sergii Volikov added a comment -

            10.2.9-MariaDB

            2017-09-28 17:32:50 5784 [ERROR] InnoDB: File \\.\C:: 'DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY)' returned OS error 250.

            Sergey_W Sergii Volikov added a comment - 10.2.9-MariaDB 2017-09-28 17:32:50 5784 [ERROR] InnoDB: File \\.\C:: 'DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY)' returned OS error 250.

            People

              wlad Vladislav Vaintroub
              amramsay Andrew Ramsay
              Votes:
              1 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.