Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: N/A
-
Fix Version/s: 10.1.2
-
Component/s: Storage Engine - InnoDB
-
Labels:
Description
Tests fail on Windows with the last revision
Revision 662701e1abfcfcdcd9d1619be2621a5d419c5905 Comments MDEV-6648: InnoDB: Add support for 4K sector size if supported New generation hard drives, SSDs and NVM devices support 4K sector size. Supported sector size can be found using fstatvfs() or GetDiskFreeSpace() functions.
See for example http://buildbot.askmonty.org/buildbot/builders/win64-release2/builds/5771/steps/test/logs/stdio
It's enough to enable InnoDB plugin and run CREATE TABLE t1 (i INT) ENGINE=InnoDB.
Does not seem to happen with XtraDB.
Does not seem to happen on Linux.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
commit 02494d9be00c35e56e97587910262c9287a18073
Author: Jan Lindström <jan.lindstrom@skysql.com>
Date: Wed Oct 29 08:39:48 2014 +0200
MDEV-6968: CREATE TABLE crashes with InnoDB pluginAnalysis: fil_extend_space_to_desired_size() does not provide file
node to os_aio(). This failed on Windows only because on Windows
we do not use posix_fallocate() to extend file space.
Fix: Add file node to os_aio() function call and make sure that
we do not use NULL pointer at os_aio_array_reserve_slot(). Additionally,
make sure that we do not use 0 as file_block_size (512 is the minimum).