Anand,
I also had this same issue after building version checked out from:
/usr/local/arch/bin/tla register-archive
http://arch.sv.gnu.org/archives/gluster/
<http://arch.sv.gnu.org/archives/gluster>
/usr/local/arch/bin/tla get -A gluster@xxxxxxxxxx
<mailto:gluster@xxxxxxxxxx> glusterfs--mainline--2.5 glusterfs
Should I be checking out mainline--2.6?
-JPH
Anand Avati wrote:
Jeff,
this bug has been fixed in the TLA version. You could either checkout
and use the snapshot, or await the next release.
avati
2007/11/24, Jeff Humes < jeff@xxxxxxxxx <mailto:jeff@xxxxxxxxx>>:
Hello. I would like to ask about having mysql data hosted on
glusterfs. Please see my issue below. I have posted DEBUG log
information on pastebin.
Thanks in advance!
-JPH
*
SERVER Version:*
glusterfsd --version
glusterfs 1.3.7 built on Nov 3 2007
*CLIENT Version:*
glusterfs --version
glusterfs 1.3.7 built on Nov 3 2007
*ISSUE:*
When hosting mysql data on glusterfs I have an issue:
The first time I start the glusterfsd server, and mount the glusterfs
client (/var/lib/mysql) mountpoint, I can start the mysql server
just fine.
Upon subsequent stop and restart of mysql it says in the mysql
logs that
it cannot lock the ibdata1 file:
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
InnoDB: Unable to lock ./ibdata1, error: 107
...
This does not happen on local disk.
http://gluster.pastebin.com/m2357e117
<http://gluster.pastebin.com/m2357e117>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxx>
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
It always takes longer than you expect, even when you take into
account Hofstadter's Law.
-- Hofstadter's Law
