glusterbot> glusterd's management port is 24007/tcp and 24008/tcp if
you use rdma. Bricks (glusterfsd) use 24009 & up for <3.4 and 49152 & up
for 3.4. (Deleted volumes do not reset this counter.) Additionally it
will listen on 38465-38467/tcp for nfs, also 38468 for NLM since 3.3.0.
NFS also d
On Mon, Oct 14, 2013 at 9:35 AM, wrote:
> centos 6.x
>
> gluster --version
>
> glusterfs 3.2.7 built on Jun 11 2012 13:22:29
>
>
>
> The problem is that when i'm trying to probe like this:
>
> gluster peer probe [hostname]
>
>
>
> It never probe's because the firewall is blocking (when I turn it
centos 6.x
gluster --version
glusterfs 3.2.7 built on Jun 11 2012 13:22:29
The problem is that when i'm trying to probe like this:
gluster peer probe [hostname]
It never probe's because the firewall is blocking (when I turn it of on both
sides everything works)
But I want to keep the
I am trying to install glusterfs on a Linux machine.
glusterfs version 3.3.2
*uname -orm*
*GNU/Linux 2.6.22-6.4.3-amd64-2527508 x86_64*
*
*
Ran* **./configure --prefix=mytempdir*
*
*
No errors reported here.
When I ran make, get this error. Any help appreciated. I am a newbie.
Thanks,
CR
*
mak
On Mon, 2013-10-14 at 07:13 +, jan.dre...@bertelsmann.de wrote:
> Hi,
>
> I'm wondering why gluster has to heal itself in the first place - as
> the underlying architicutre is a RAID5, that one should repair itself
> and gluster should not notice a defect - or does "heal" mean
> "re-sync"?!
He
On 14 October 2013 13:26, Vijay Bellur wrote:
> volume specific extended attributes are written on brick directories at
> the time of volume creation. This information is subsequently used for
> validation at the time of starting a volume.
>
> Do you really want to create/start a brick on a peer
Hi David,
Thanks for your reply.
There are lot of files and sub-directorys under them.
The problem is it takes around 10min to display the contents once I use ls
command which is not normal.
--
Regards,
Pramod
From: David Gibbons [mailto:david.c.gibb...@gmail.com]
Sent: Monday, October 07, 2
On 10/02/2013 06:05 PM, Jeff Darcy wrote:
On 10/02/2013 06:57 AM, Heggland, Christian wrote:
Unsure if its recommended but you could try and do the following if
the set command stops adding / removing settings:
1. Stop the volume 2. Edit the config file for that volume on each
node ( /var/lib/g
On 10/08/2013 05:50 PM, Maciej Gałkiewicz wrote:
Hi
Is it possible to create volume even though one of bricks is down? I
have automated the process of creating volumes and downtime of the brick
breaks it.
volume specific extended attributes are written on brick directories at
the time of vol
Hi,
I am running the glusterFS 3.4.1 NFS server. I have created a distributed
volume on server 1 , and I am trying to mount the soft link contained in
the volume as NFS from server 2 . but it is failing with the error "
mount.nfs: an incorrect mount option was specified"
Below is the volume i
On 10/11/2013 10:20 AM, Dan Mons wrote:
Following up on this:
* GlusterFS 3.4.1 solves the problem of renaming over CIFS from a
Windows client (via Samba3 and vfs_glusterfs/libgfapi). Happy days!
* I still see 4 lines of this sort of thing for each file read in
/var/log/glusterfs/bricks/*.log:
Hi,
I'm wondering why gluster has to heal itself in the first place - as the
underlying architicutre is a RAID5, that one should repair itself and gluster
should not notice a defect - or does "heal" mean "re-sync"?!
Regards
Jan
Von: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun
12 matches
Mail list logo
