[MDEV-17485] [Draft] InnoDB: Operating system error number 80 in a file operation Created: 2018-10-17  Updated: 2018-10-17

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Unresolved Votes: 0
Labels: None

Attachments: File mysql.err     File mysql.log.gz     File trial6.log    

 Description   

http://buildbot.askmonty.org/buildbot/builders/qa-win-rel/builds/5419/steps/result_summary/logs/stdio

10.3 97a37edc970f8619ffd23394b61fe310d705d0ef

2018-10-16 22:06:51 0 [Note] D:\qa-win-rel\install\bin\mysqld.exe: ready for connections.
Version: '10.3.11-MariaDB-log'  socket: ''  port: 11400  Source distribution
2018-10-16 22:07:41 16 [Note] Detected table cache mutex contention at instance 1: 20% waits. Additional table cache instance activated. Number of instances after activation: 2.
2018-10-16 22:08:16 22 [ERROR] InnoDB: Cannot save table statistics for table `test`.`seq2`: Lock wait timeout
2018-10-16 22:08:17 18 [ERROR] InnoDB: Cannot save table statistics for table `test`.`seq2`: Lock wait timeout
2018-10-16 22:08:18 19 [ERROR] InnoDB: Cannot save table statistics for table `test`.`seq2`: Lock wait timeout
2018-10-16 22:10:29 20 [ERROR] InnoDB: Operating system error number 80 in a file operation.
2018-10-16 22:10:29 20 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2018-10-16 22:10:29 20 [Note] InnoDB: The file '.\test\seq3.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. You can resolve the problem by removing the file.
2018-10-16 22:10:29 20 [ERROR] InnoDB: Cannot create file '.\test\seq3.ibd'

13b38fc3422c0a89a74ebde9856377be3b99df32

perl E:\buildbot\rqg/runall-new.pl --grammar=conf/runtime/information_schema.yy --gendata-advanced --skip-gendata --no-mask --queries=100M --duration=350 --threads=6 --seed=1539727604 --views --vcols --reporters=Backtrace,ErrorLog,Deadlock --validators=TransformerNoComparator --transformers=ExecuteAsCTE,ExecuteAsDeleteReturning,ExecuteAsExcept,ExecuteAsExecuteImmediate,ExecuteAsInsertSelect,ExecuteAsIntersect,ExecuteAsUnion,ExecuteAsUpdateDelete,ExecuteAsView,ExecuteAsPreparedTwice,ExecuteAsSPTwice --redefine=conf/mariadb/general-workarounds.yy --redefine=conf/mariadb/alter_table.yy --redefine=conf/mariadb/bulk_insert.yy --redefine=conf/mariadb/xa.yy --redefine=conf/mariadb/versioning.yy --redefine=conf/mariadb/sequences.yy --mysqld=--log_output=FILE --mysqld=--log-bin --mysqld=--log_bin_trust_function_creators=1 --mysqld=--loose-max-statement-time=30 --mysqld=--loose-debug_assert_on_not_freed_memory=0 --mysqld=--default-storage-engine=MyISAM --engine=MyISAM --mtr-build-thread=140 --basedir1=D:\qa-win-rel\install --vardir1=E:\buildbot\vardirs\qa-win-rel\10.3-5419\optim-combo/current1_1

Not reproducible right away.



 Comments   
Comment by Vladislav Vaintroub [ 2018-10-17 ]

Some operating system numbers are described in https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes
According to https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes--0-499-

ERROR_FILE_EXISTS
80 (0x50)
The file exists.

Comment by Elena Stepanova [ 2018-10-17 ]

Yes, that's what the subsequent error (or rather Note) message says in the excerpt above:

2018-10-16 22:10:29 20 [Note] InnoDB: The file '.\test\seq3.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. You can resolve the problem by removing the file.

By the way, it doesn't look like a "Note", more like a warning at least.

Generated at Thu Feb 08 08:36:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.