similar to: Gluster 3.2 configurations + translators

Displaying 20 results from an estimated 10000 matches similar to: "Gluster 3.2 configurations + translators"

2012 Jan 22
2
Best practices?
Suppose I start building nodes with (say) 24 drives each in them. Would the standard/recommended approach be to make each drive its own filesystem, and export 24 separate bricks, server1:/data1 .. server1:/data24 ? Making a distributed replicated volume between this and another server would then have to list all 48 drives individually. At the other extreme, I could put all 24 drives into some
2011 Jun 06
2
Gluster 3.2.0 and ucarp not working
Hello everybody. I have a problem setting up gluster failover funcionality. Based on manual i setup ucarp which is working well ( tested with ping/ssh etc ) But when i use virtual address for gluster volume mount and i turn off one of nodes machine/gluster will freeze until node is back online. My virtual ip is 3.200 and machine real ip is 3.233 and 3.5. In gluster log i can see: [2011-06-06
2011 Jul 20
1
Top Reset
Hello, is there any way how to reset volume TOP statistics ? thanks Matus
2017 Jun 12
3
After gluster clean up sub directories becomes invisible
can you please describe a bit more about the steps taken to clean up and re-configure gluster? Regards, Vijay On Mon, Jun 12, 2017 at 12:08 PM, Sangeeta Ramapure < sangeeta.ramapure at globallogic.com> wrote: > Kindly somebody help me with this issue. > > > > Thanks & Regards, > > Sangeeta Ramapure > > > > *From:* Sangeeta Ramapure
2017 Oct 24
0
brick is down but gluster volume status says it's fine
On Tue, Oct 24, 2017 at 11:13 PM, Alastair Neil <ajneil.tech at gmail.com> wrote: > gluster version 3.10.6, replica 3 volume, daemon is present but does not > appear to be functioning > > peculiar behaviour. If I kill the glusterfs brick daemon and restart > glusterd then the brick becomes available - but one of my other volumes > bricks on the same server goes down in
2017 Oct 24
2
brick is down but gluster volume status says it's fine
gluster version 3.10.6, replica 3 volume, daemon is present but does not appear to be functioning peculiar behaviour. If I kill the glusterfs brick daemon and restart glusterd then the brick becomes available - but one of my other volumes bricks on the same server goes down in the same way it's like wack-a-mole. any ideas? [root at gluster-2 bricks]# glv status digitalcorpora > Status
2008 Nov 09
3
Still problem with trivial self heal
Hi! I have trivial problem with self healing. Maybe somebody will be able to tell mi what am I doing wrong, and why do the files not heal as I expect. Configuration: Servers: two nodes A, B --------- volume posix type storage/posix option directory /ext3/glusterfs13/brick end-volume volume brick type features/posix-locks option mandatory on subvolumes posix end-volume volume server
2017 Jul 10
2
[Gluster-devel] gfid and volume-id extended attributes lost
Please use the systemtap script( https://paste.fedoraproject.org/paste/EGDa0ErwX0LV3y-gBYpfNA) to check which process is invoking remove xattr calls. It prints the pid, tid and arguments of all removexattr calls. I have checked for these fops at the protocol/client and posix translators. To run the script .. 1) install systemtap and dependencies. 2) install glusterfs-debuginfo 3) change the path
2017 Oct 04
0
Glusterd not working with systemd in redhat 7
On Wed, Oct 04, 2017 at 12:17:23PM +0000, ismael mondiu wrote: > > Thanks Niels, > > We want to install it on redhat 7. We work on a secured environment > with no internet access. > > We download the packages here > https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.10/ and > then, we push the package to the server and install them via rpm > command .
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
Hello , it seems the problem still persists on 3.10.6. I have a 1 x (2 + 1) = 3 configuration. I upgraded the first server and then launched a reboot. Gluster is not starting. Seems that gluster starts before network layer. Some logs here: Thanks [2017-10-04 15:33:00.506396] I [MSGID: 106143] [glusterd-pmap.c:277:pmap_registry_bind] 0-pmap: adding brick /opt/glusterfs/advdemo on port
2017 Oct 04
0
Glusterd not working with systemd in redhat 7
On Wed, Oct 04, 2017 at 09:44:44AM +0000, ismael mondiu wrote: > Hello, > > I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is the correct way to upgrade from 3.10.5 to 3.10.6. > > It's hard to find upgrade guides for a minor release. Can you help me please ? Packages for GlusterFS 3.10.6 are available in the testing repository of the
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
Thanks Niels, We want to install it on redhat 7. We work on a secured environment with no internet access. We download the packages here https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.10/ and then, we push the package to the server and install them via rpm command . Do you think this is a correct way to upgrade gluster when working without internet access? Thanks in advance
2017 Oct 05
0
Glusterd not working with systemd in redhat 7
On Wed, Oct 4, 2017 at 9:26 PM, ismael mondiu <mondiu at hotmail.com> wrote: > Hello , > > it seems the problem still persists on 3.10.6. I have a 1 x (2 + 1) = 3 > configuration. I upgraded the first server and then launched a reboot. > > > Gluster is not starting. Seems that gluster starts before network layer. > > Some logs here: > > > Thanks >
2017 Oct 05
2
Glusterd not working with systemd in redhat 7
Hello Atin, Please find below the requested informations: [root at dvihcasc0r ~]# cat /var/lib/glusterd/vols/advdemo/bricks/* hostname=dvihcasc0r path=/opt/glusterfs/advdemo real_path=/opt/glusterfs/advdemo listen-port=49152 rdma.listen-port=0 decommissioned=0 brick-id=advdemo-client-0 mount_dir=/advdemo snap-status=0 hostname=dvihcasc0s path=/opt/glusterfs/advdemo
2017 Nov 06
2
Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.
Do the users have permission to see/interact with the directories, in addition to the files? On Mon, Nov 6, 2017 at 1:55 PM, Nithya Balachandran <nbalacha at redhat.com> wrote: > Hi, > > Please provide the gluster volume info. Do you see any errors in the > client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? > > > Thanks, > Nithya > > On 6
2017 Sep 01
2
peer rejected but connected
Logs from newly added node helped me in RCA of the issue. Info file on node 10.5.6.17 consist of an additional property "tier-enabled" which is not present in info file from other 3 nodes, hence when gluster peer probe call is made, in order to maintain consistency across the cluster cksum is compared. In this case as both files are different leading to different cksum, causing state in
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
Hello, I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is the correct way to upgrade from 3.10.5 to 3.10.6. It's hard to find upgrade guides for a minor release. Can you help me please ? Thanks in advance Ismael ________________________________ De : Atin Mukherjee <amukherj at redhat.com> Envoy? : dimanche 17 septembre 2017 14:56 ? : ismael
2017 Sep 17
2
Glusterd not working with systemd in redhat 7
The backport just got merged few minutes back and this fix should be available in next update of 3.10. On Fri, Sep 15, 2017 at 2:08 PM, ismael mondiu <mondiu at hotmail.com> wrote: > Hello Team, > > Do you know when the backport to 3.10 will be available ? > > Thanks > > > > > ------------------------------ > *De :* Atin Mukherjee <amukherj at
2012 Nov 30
3
Cannot mount gluster volume
Hi, We recently installed glusterfs 3.3.1. We have a 3 brick gluster system running that was being successfully mounted earlier. Yesterday we experienced a power outage and now after rebooting our systems, we are unable to mount this gluster file system. On the gluster client, a df -h command shows 41TB out of 55TB, while an ls command shows broken links for directories and missing files.
2017 Aug 17
3
Glusterd not working with systemd in redhat 7
Hi Team, I noticed that glusterd is never starting when i reboot my Redhat 7.1 server. Service is enabled but don't works. I tested with gluster 3.10.4 & gluster 3.10.5 and the problem still exists. When i started the service manually this works. I'va also tested on Redhat 6.6 server and gluster 3.10.4 and this works fine. The problem seems to be related to Redhat 7.1 This is