Gluster users - Jul 2015 - GlusterFS test from manual compilation

Hi,

I would like to test GlusterFS with only 1 brick in order to have quota
but without preinstalled packages.

So, I compiled glusterfs-3.6.1.tar.gz with :

# COMPILATION
./configure --prefix=/efr/glusterfs-3.6.1
make

# INSTALLATION
make install
ln -s glusterfs-3.6.1 /efr/glusterfs

# VERIFICATION
/efr/glusterfs/sbin/glusterfs --version
glusterfs 3.6.1 built on Nov 14 2014 23:50:54

# CONFIGURATION
/efr/glusterfs/sbin/glusterd
mkdir -p /home/gluster/exp1
/efr/glusterfs/sbin/gluster volume create test-volume
192.168.0.250:/home/gluster/exp1 force

/efr/glusterfs/sbin/gluster volume info

Volume Name: test-volume
Type: Distribute
Volume ID: 6f3186cf-8668-4a0c-a4eb-e7ce0ebb58a9
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 192.168.0.250:/home/gluster/exp1

/efr/glusterfs/sbin/gluster volume start test-volume

# MOUNT : FAILED
mkdir /mnt/glusterfs
/efr/glusterfs/sbin/glusterfs --debug --volfile-server=192.168.0.250
--volume-name=test-volume /mnt/glusterfs

No output for this command, no log, and :
echo $?
255

What is the problem ?

Thanks you for any help ...

Yves

-Atin
Sent from one plus one
On Jul 12, 2015 6:52 PM, Yves R?veillon - eurower.fr <
yves.reveillon at eurower.fr> wrote:
>
> Hi,
>
> I would like to test GlusterFS with only 1 brick in order to have quota
> but without preinstalled packages.
>
> So, I compiled glusterfs-3.6.1.tar.gz with :
>
> # COMPILATION
> ./configure --prefix=/efr/glusterfs-3.6.1
> make
>
> # INSTALLATION
> make install
> ln -s glusterfs-3.6.1 /efr/glusterfs
>
> # VERIFICATION
> /efr/glusterfs/sbin/glusterfs --version
> glusterfs 3.6.1 built on Nov 14 2014 23:50:54
>
> # CONFIGURATION
> /efr/glusterfs/sbin/glusterd
> mkdir -p /home/gluster/exp1
> /efr/glusterfs/sbin/gluster volume create test-volume
> 192.168.0.250:/home/gluster/exp1 force
>
> /efr/glusterfs/sbin/gluster volume info
>
> Volume Name: test-volume
> Type: Distribute
> Volume ID: 6f3186cf-8668-4a0c-a4eb-e7ce0ebb58a9
> Status: Started
> Number of Bricks: 1
> Transport-type: tcp
> Bricks:
> Brick1: 192.168.0.250:/home/gluster/exp1
>
> /efr/glusterfs/sbin/gluster volume start test-volume
>
> # MOUNT : FAILED
> mkdir /mnt/glusterfs
> /efr/glusterfs/sbin/glusterfs --debug --volfile-server=192.168.0.250
> --volume-name=test-volume /mnt/glusterfs
>
> No output for this command, no log, and :
> echo $?
> 255
Does the below command also fail?

mount -t glusterfs 192.168.0.250:test-volume /mnt/glusterfs
>
> What is the problem ?
>
> Thanks you for any help ...
>
> Yves
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150712/270cc90f/attachment.html>

On Sun, Jul 12, 2015 at 6:52 PM, "Yves R?veillon - eurower.fr"
<yves.reveillon at eurower.fr> wrote:
> # MOUNT : FAILED
> mkdir /mnt/glusterfs
> /efr/glusterfs/sbin/glusterfs --debug --volfile-server=192.168.0.250
> --volume-name=test-volume /mnt/glusterfs
>
> No output for this command, no log, and :
> echo $?
> 255
>
The correct option to specify the volume name is `--volfile-id` not
`--volume-name`.
Your command line should look like,
`<path>/glusterfs --volfile-server=192.168.0.250
--volfile-id=test-volume /mnt/glusterfs`

I've dropped the `--debug` as it forces glusterfs to run in foreground
mode, which is not what many people want. If you would like to get
debug logs, use `--log-level=DEBUG`.