Re.
Marko Jung wrote:
Gordan Bobic wrote:
2) You may have bumped into a GFS2 bug. What distro/cluster version are you
running? GFS2 was "preview only" until very recently, and the pace of
development and fixes in it are still a tad too high for a production
system for my liking. Is there any particular reason why you can't use
GFS1?
It is CentOS 5.3 final without any fancy external updates or similar stuff.
We chose GFS2 because it is the default with RHEL 5.3.
I thought I should be more verbose on what I am trying to achieve MySQL
associated to a floating IP running on cluster as failover. Storage and
configuration should reside on a huge GFSv2 Filesystem.
I used the distribution provided MySQL packages and used the following my.cnf:
------%<-----------------------------------
[mysqld]
datadir=/san/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
skip-innodb
enable-locking
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
------%<-----------------------------------
In addition to this i modified the /usr/bin/mysqld_safe to use
--external-locking as option.
mysql.log shows the following error:
------%<-----------------------------------
090804 17:13:25 mysqld started
090804 17:13:25 [ERROR] bdb: /san/mysql: Permission denied
090804 17:13:25 [ERROR] bdb: /san/mysql/log.0000000001: Permission denied
090804 17:13:25 [ERROR] bdb: PANIC: Permission denied
090804 17:13:25 [ERROR] bdb: PANIC: DB_RUNRECOVERY: Fatal error, run
database recovery
090804 17:13:25 [ERROR] bdb: fatal region error detected; run recovery
090804 17:13:25 [ERROR] bdb: /san/mysql: Permission denied
090804 17:13:25 [ERROR] Fatal error: Can't open and lock privilege tables:
Table 'host' is read only
------%<-----------------------------------
But permissions are right (everything owned by mysql user, group mysql).
I am a bit confused - the identical configuration on an ext3 filesystem
works fine.
Marko
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
