Bug #92728 MySQL 5.7 issue with 16TB disk
Submitted: 10 Oct 2018 8:39 Modified: 8 Jan 2019 13:31
Reporter: Bertrand Bram Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Partitions Severity:S3 (Non-critical)
Version:5.7.20 OS:Windows (WIndows Server 2016)
Assigned to: CPU Architecture:x86 (On a VM)
Tags: disk size, partitioning

[10 Oct 2018 8:39] Bertrand Bram
Description:
When creating a partitioned table with data directory explicitly set on a disk with capacity > 16TB, *.idb file is not created on the disk but rather on default MySQL Data directory.
Everything works fine if disk capacity <= 16TB

(Note: this is not a innodb_page_size issue, as it is set to default 16K value, and is only related to the maximum size of the files, not to the disk capacity itself)

How to repeat:
1) Have a MySQL 5.7.20 running on a Windows Server 2016 Virtual Machine with two disks from a NAS: C:\ for system and D:\ for data (empty at start, size > 16TB)
2) Create a partitioned table
DROP DATABASE IF EXISTS `PROFILES`;
CREATE DATABASE `PROFILES` DEFAULT CHARACTER SET latin1;
use `PROFILES`;

CREATE TABLE PROFILES.ACQUISITION (
    Id int(10) unsigned NOT NULL AUTO_INCREMENT,
    PRIMARY KEY (Id)
)
PARTITION BY RANGE COLUMNS(id) (
       PARTITION p_MAXVALUE VALUES LESS THAN(MAXVALUE)
       DATA DIRECTORY = 'D:\\MyDataBase'
); 
3) Directory D:\MyDataBase\profiles is created but profiles#acquisition#p_maxvalue.ibd file is stored in the default MySQL Data directory\profiles, on C: and not on D:
4) select * from information_schema.INNODB_SYS_TABLESPACES where name like '%profile%';
returns nothing
[10 Oct 2018 10:38] Bertrand Bram
Note: storage engine is InnoDB
[5 Dec 2018 14:26] MySQL Verification Team
Hi,

Thank you for your bug report.

Can you please take look where is a location for your `datadir` configured ???

Thanks in advance.
[6 Jan 2019 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".