Hi,
Did you happen to file a bugreport for MySQL (at bugs.mysql.com) as well?
Here it is.
http://bugs.mysql.com/bug.php?id=75616
I found the cause of the issue. FreeBSD doesn't present disks as block devices but instead as character devices.
https://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-block.html
"case S_IFCHR:" should be added directly above or below "case S_IFBLK:" here.
http://bazaar.launchpad.net/~mysql/mysql-server/5.6/view/head:/storage/innobase/os/os0file.cc#L3167
####
What do I need to do to get this fix merged in? Thanks.
Is there anything I can do to get this looked at? I can try patching it and compiling on FreeBSD, it should be pretty easy to do so from ports if you need me to verify the fix I proposed works.
Also this affects linux as well, if a char device is used.
In cases like this we generally wait for an upstream bug fix to avoid complex code merges.
Unless upstream refuses to fix the bug, of course.
It looks like this was fixed in mysql 5.6.25
https://github.com/mysql/mysql-server/commit/aee6bc8ed15e14fb2a532cd0ebffa0ec161c0e77
I haven't had a chance to test it yet, but will as soon as the FreeBSD mysql56 port is updated to 5.6.25
When applying this changes to mariadb I think these need to also be applied to the storage/xtradb versions of the files. Finally, I'd very happy if this can be backported to mariadb10.0 
I made a PR for the 10.0 branch here. It might also cleanly apply to 10.1
https://github.com/MariaDB/server/pull/85
PR merged by jplindst