*
Here is the procedure I used to install:
# Get source:*
cd /usr/src/INSTALL_GLUSTER_UPGRADE
/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
cd glusterfs
./autogen.sh
mkdir build
cd build
# SERVER ONLY:
../configure --disable-ibverbs
# CLIENT ONLY:
../configure --disable-ibverbs --disable-server
make install
*#----------------------------------------
Here is the output of the checkout:*
[root@asknglpr01 INSTALL_GLUSTER_UPGRADE]# /usr/local/arch/bin/tla get
-A gluster@xxxxxxxxxx glusterfs--mainline--2.5 glusterfs
WARNING: no rule found for checking signatures from gluster@xxxxxxxxxx
Consider creating ~/.arch-params/signing/gluster@xxxxxxxxxx.check
or ~/.arch-params/signing/=default.check
* from archive cached:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-516
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-517
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-518
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-519
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-520
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-521
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-522
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-523
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-524
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-525
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-526
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-527
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-528
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-529
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-530
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-531
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-532
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-533
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-534
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-535
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-536
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-537
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-538
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-539
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-540
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-541
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-542
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-543
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-544
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-545
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-546
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-547
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-548
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-549
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-550
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-551
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-552
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-553
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-554
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-555
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-556
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-557
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-558
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-559
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-560
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-561
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-562
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-563
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-564
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-565
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-566
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-567
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-568
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-569
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-570
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-571
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-572
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-573
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-574
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-575
* patching for revision:
gluster@xxxxxxxxxx/glusterfs--mainline--2.5--patch-576
* making pristine copy
* tree version set gluster@xxxxxxxxxx/glusterfs--mainline--2.5
**
-JPH
Anand Avati wrote:
Jeff,
what patchset did you try with?
avati
2007/11/24, Jeff Humes <jeff@xxxxxxxxx <mailto:jeff@xxxxxxxxx>>:
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>
<mailto: 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>
<mailto: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>
<mailto:Gluster-devel@xxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxx>>
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
<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
--
It always takes longer than you expect, even when you take into
account Hofstadter's Law.
-- Hofstadter's Law
