[MDEV-13558] OS Error 201 appears in MariaDB log Created: 2017-08-17  Updated: 2017-08-17  Resolved: 2017-08-17

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.2.7
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Stuart Slater Assignee: Vladislav Vaintroub
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Windows 2008 R1 (32bit) running as VM on ESXi 6.0 hypervisor.

Issue Links:
Duplicate
duplicates MDEV-12948 ERROR in log file: IOCTL_STORAGE_QUER... Closed

 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?

 Comments   
Comment by Vladislav Vaintroub [ 2017-08-17 ]

Hi Stuart,
none of this errors are fatal in any way.

  • Perhaps the storage driver does not implement IOCTL_STORAGE_QUERY_PROPERTY. Odd, but we still have fallback in code if this does not work.
    I think we should improve on this message by not writing this message repeatedly. Writing it as note, or not writing it at all.
  • Aborted connection : do you have an error in your application?Does Hibernate log anything?There are several possible causes, I can think of two - client application terminates or closes socket, without saying goodbye to the server (i.e without sending COM_QUIT), or wait_timeout has exceeded (maybe in a pooled hibernate connection), in which case we can do a better message that this. If you do not like this messages to be written, you can use log_warnings=0, although you might miss something important with that setting.
Generated at Thu Feb 08 08:06:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.