[Gluster-users] volume creation safe on existing volume?
Hi. If one were to use the volume creation and start commands on an existing volume, would that be safe and leave the currently existing volume in a good state with all data intact? For example, if an automation script tries to re-create a volume that already exists. -G ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] GMC, ssh and rrd
Hi. The current 1.0.0a release of GMC on Centos has an issue where calls to retreive rrd data via SSH fail because a tty is required for such a call, but the GMC does not force tty allocation. What is the recommended way around that? -G -- Geoff Galitz, ggal...@shutterstock.com WebOps Engineer, Europe Shutterstock Images http://.shutterstock.com/ ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] avoiding split brains
Here is basic question: Are we more likely to avoid a split brain scenario if we have more than 2 bricks total? IOW, one brick on at least three servers or more? Thanks. -Geoff -- Geoff Galitz, ggal...@shutterstock.com WebOps Engineer, Europe Shutterstock Images http://.shutterstock.com/ ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] [3.3 beta3] When should the self-heal daemon be triggered?
I then ran the command: gluster volume heal testvol After I ran that, there was some activity, and now all the files were populated. Was that supposed to happen automatically, eventually, or am I missing something about how the self-heal daemon works? The self-heal daemon triggers a crawl once every 600 seconds. If you wait out that interval, you should be able to see self-heals happening automatically. Else you can trigger it explicitly the way you did. As a follow-up question to that: does this all apply to gluster 3.2.4 also? And if you manually trigger a self-heal (via doing a find + stat as some of us were originally trained) multiple times within a 10 minute window, will that cause a problem? Geoff Galitz, ggal...@shutterstock.com WebOps Engineer, Europe Shutterstock Images http://.shutterstock.com/ ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] connection refused errors
Hi. I am seeing lots of these messages: [root@prod-forum01.ma01 glusterfs]# tail -f etc-glusterfs-glusterd.vol.log [2012-04-24 09:19:04.103241] E [socket.c:2080:socket_connect] 0-management: connection attempt failed (Connection refused) [2012-04-24 09:19:07.103698] E [socket.c:2080:socket_connect] 0-management: connection attempt failed (Connection refused) [2012-04-24 09:19:10.104283] E [socket.c:2080:socket_connect] 0-management: connection attempt failed (Connection refused) My cluster is also not so healthy. It has two bricks configured as replicated, but when brick2 crashes (full root filesystem, for example) everything seems to go offline. Related? Thanks. -- Geoff Galitz, ggal...@shutterstock.com WebOps Engineer, Europe Shutterstock Images http://.shutterstock.com/ ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Fuse problem
I have fuse.x86_64 2.7.4-1.el5.rf installed but: # modprobe fuse FATAL: Module fuse not found. That is the userland part of fuse. There is also a kernel module that you will need to get and install. I'm guessing you have yum since this appears to be a RHEL 5 machine so try a 'yum search fuse' to see if you can find the name of the kernel module. It escapes me at the moment, which is why I suggest the yum search. You are looking for the dkms-fuse package, available over yum. You may need to go to rpmforge to get it. -geoff - Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/ ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
