zfs discuss - Nov 2005 - Problems with compiling and using MySQL from a ZFS volume

To all:

Eager to "play" with ZFS I set up a Blade 100 with a MultiPack that
has six 36 GB disks and created a raidz volume called array. I then created two
mount points, /mysql and /export/home. I compiled MySQL 5.0.15 in /export/home
and installed it in /mysql. The problem is that when I attempt to start the
mysqld process I get the following in the error log:

InnoDB: Operating system error number 2 is a file operation.
InnoDB: File name /array/mysql/var/ibdata1
InnoDB: File operation call: ''create''
InnoDB: Cannot continue operation.

Is there something I missed when I created the mount points (using zfs set
mountpoint=/mysql /array/mysql )? I checked the config.log for mysql and it does
not show the path array anywhere, so I am at a loss as to how MySQL thinks
/array is the actual mountpoint.

Thanks
This message posted from opensolaris.org

On Mon 21 Nov 2005 at 05:42AM, Robert Escue wrote:
> To all:
> 
> Eager to "play" with ZFS I set up a Blade 100 with a MultiPack
that
> has six 36 GB disks and created a raidz volume called array. I then
> created two mount points, /mysql and /export/home. I compiled MySQL
> 5.0.15 in /export/home and installed it in /mysql. The problem is that
> when I attempt to start the mysqld process I get the following in the
> error log:
> 
> InnoDB: Operating system error number 2 is a file operation.
> InnoDB: File name /array/mysql/var/ibdata1
> InnoDB: File operation call: ''create''
> InnoDB: Cannot continue operation.
> 
> Is there something I missed when I created the mount points (using zfs
> set mountpoint=/mysql /array/mysql )? I checked the config.log for
> mysql and it does not show the path array anywhere, so I am at a loss
> as to how MySQL thinks /array is the actual mountpoint.
You might do a ''truss -o /tmp/truss.out -fa'' on the start of
the mysql
instance, and put the /tmp/truss.out log somewhere we could take a look.

"Operating system error number 2", though, looks like 

ENOENT  2       "No such file or directory"

So perhaps you''ve made a configuration error and some file or enclosing
directory it wants is missing?

        -dp

-- 
Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp

Dan,

Thanks, I found a line in /etc/my.cnf I had missed (D''oh)!
This message posted from opensolaris.org