[MDEV-13941] Innodb/Windows, 10.2 : High NTFS fragmentation Created: 2017-09-28  Updated: 2017-12-05  Resolved: 2017-09-30

Status: Closed
Project: MariaDB Server
Component/s: Platform Windows, Storage Engine - InnoDB
Affects Version/s: 10.2
Fix Version/s: 10.2.10

Type: Bug Priority: Major
Reporter: Vladislav Vaintroub Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-13612 Startup takes longer than 5 - 50 minu... Closed
relates to MDEV-14554 MariaDB server 10.2.10 doesn't repond... Closed
relates to MDEV-11520 Extending an InnoDB data file unneces... Closed
relates to MDEV-14244 MariaDB 10.2.10 fails to run on Debia... Closed

 Description   

High NTFS fragmentation, and IO error was reported by on stackexchange
https://dba.stackexchange.com/questions/186895/ntfs-filesystem-fragmentation-issue-occur-after-migrating-mysql-5-6-database-to

This is for 10.2. There are 2 things that have changed as compared with to previous version

  1. all files are made sparse "when opening", this was ported from Innodb 5.7
  2. when tablespace is extended, we do not write binary zeros anymore to the file, but instead
    SetFileInformationByHandle with FileEndOfFileInfo

Together, those changes might create a "hole" at the end of file, even if compression is not on. Also some investigation should be done on whether to write binary zeroes is necessary, and on how exactly to grow file. There are several options - write zeroes, SetEndOfFile, SetFileInformationByHandle(), DeviceIoControl(FSCTL_SET_ZERO_RANGE) . Some details can be found in https://stackoverflow.com/questions/46458151/setendoffile-vs-setfileinformationbyhandle-to-extend-file)



 Comments   
Comment by Vladislav Vaintroub [ 2017-09-30 ]

https://github.com/MariaDB/server/commit/96b9c617870edf6cdbac1e7ed1cd56a33bf39656

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