Date: Mon, 19 Jan 2015 15:10:57 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196895] databases/mariadb100 raw device not working as InnoDB data file Message-ID: <bug-196895-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196895 Bug ID: 196895 Summary: databases/mariadb100 raw device not working as InnoDB data file Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: joshruehlig@gmail.com Creating a new InnoDB data file, or using an existing InnoDB data file, with a raw device isn't working with mariadb100-server-10.0.15. ##CONFIG## innodb_data_home_dir= innodb_data_file_path = /dev/zvol/zroot/test:8G(new)raw ##ERROR## [ERROR] InnoDB: '/dev/zvol/zroot/test' not a regular file. #### ########## This works as expected with mariadb55-server. Apparently this was fixed with in version 10.0.11, but maybe the patch to os_file_get_status doesn't work for FreeBSD or ZFS ZVOLs. https://mariadb.atlassian.net/browse/MDEV-6057 Looking at the comments, a Debian user also had a problem, on version 10.0.15, with raw partitions on LVM (linux software raid). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196895-13>