Comment 1 for bug 1578604

Sveta, a tentative fix produces the following output in the error log, please check if OK (the very first and the very last lines come from context that is likely to be different in the real occurences, this is a simulated testcase error). The line with innodb_log_block_size is only printed if the variable has a non-default value.

InnoDB: Database physically writes the file full: wait...
160506 15:16:43 InnoDB: Error: Write to file ./ib_logfile0 failed at offset 0 0.
InnoDB: 1048576 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 22.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: the error might be caused by redo log I/O not satisfying innodb_flush_method=ALL_O_DIRECT requirements by the underlying file system.
InnoDB: this might be caused by an incompatible non-default innodb_log_block_size value 4096.
InnoDB: please file a bug at https://bugs.percona.com and include this error message, my.cnf settings, and information about the file system where the redo log resides.
InnoDB: a possible workaround is to change innodb_flush_method value to something else than ALL_O_DIRECT.
InnoDB: Error in creating ./ib_logfile0: probably out of disk space
160506 15:16:43 [ERROR] Plugin 'InnoDB' init function returned error.