Issue is already being track by Jan, just summarizing some offline discussions with Jan..

Code in “storage/innobase/os/os0file.cc” is currently tuned for 512Byte sector size and the same need to be support file-system block-size 4K/8K/other sector sizes.

Required set of changes..

• call to fstat/fstatvfs() be added for the first invocation of fallocate() on individual file/table enabled for NVM compression.
• queried “st_blksize/f_bsize” be used to determine
  — required alignments for file I/O block size.
  — required alignment for the PTRIM as required.
• Any subsequent io_submit/PTRIM uses the per-file, stashed values for alignment.

This should be a gating item for the release.

commit 662701e1abfcfcdcd9d1619be2621a5d419c5905
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Tue Oct 28 14:49:31 2014 +0400

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.

revno: 3998
committer: Jan Lindström <jplindst@mariadb.org>
branch nick: 10.0-FusionIO-release
timestamp: Wed 2014-10-29 08:51:17 +0200
message:
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.