Hi Everyone,
I'm trying to set up Gluster 3.3.0 on a fresh CentOS 6.2 with selinux
firewall disabled, hosts can see each other (they are present in DNS and
one can ping/telnet to gluster port each other), there seems to be nothing
suspicious in sysctl, but whatever I put in peer probe refers to
with: 0
Hope it makes any sense.
Any ideas?
Thanks in advance,
Vladimir.
On Mon, Jul 2, 2012 at 5:32 PM, Marcelo Roccasalva roc...@gmail.com wrote:
On Mon, Jul 2, 2012 at 8:32 AM, Vladimir Yakovlev mrque...@gmail.com
wrote:
Hi Everyone,
I'm trying to set up Gluster 3.3.0 on a fresh
b.cand...@pobox.com wrote:
On Mon, Jul 02, 2012 at 05:54:46PM +0400, Vladimir Yakovlev wrote:
I tried different configurations, the latest follows:
[root@host1 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
127.0.0.1 host1
(nsswitch.conf order resp.) file - but
gluster does, as does ping and anything else using gethostbyname(3)
hth,
Philip
2012/7/2 Vladimir Yakovlev mrque...@gmail.com:
Thanks, Brian, for the hint.
I've changed /etc/hosts with respect to your comment, but it didn't help
either.
The problem
busy ;-)
BR,
Vladimir.
On Mon, Jul 2, 2012 at 6:34 PM, Vladimir Yakovlev mrque...@gmail.comwrote:
Hi Philip,
I tried IPs instead of hostnames at the beginning, but it didn't help:
[root@host1 ~]# gluster peer probe 192.168.1.193
Probe on localhost not needed
My assumption is smth wrong
vbel...@redhat.com wrote:
On 07/04/2012 12:41 PM, Vladimir Yakovlev wrote:
Hi Everyone,
I've just set up 2 machines with Gluster in Replica mode: # gluster
volume create DATA replica 2 transport tcp host1:/mnt/DATA
host2:/mnt/DATA ; # gluster volume start DATA
Whenever I create a test file
OK, got it.
Thanks!
On Wed, Jul 4, 2012 at 3:15 PM, Vijay Bellur vbel...@redhat.com wrote:
On 07/04/2012 02:10 PM, Vladimir Yakovlev wrote:
OK, got it, thanks.
So Gluster will not replicate files itself, but I should use rsync
instead. Right?
rsyncing between bricks is not recommended
Hi Everyone,
I have 2 machines with 3x2TB disks, which are almost full with files and
synced (e.g. sdb1 on machine1 is packed with files, which are the same on
machine2 sdb1, and the same is valid for other 2 disks).
What is the best practice to setup Gluster on these machines, so that I
could
Hi Everyone,
I was running GlusterFS 3.3.1 on ext4 with CentOS 6.3, but it ran out of
memory quickly because of known bug in 64/32 bits operations with ext4.
I built another machine with XFS and added it to volume, after full heal,
switched to the new machine.
The configuration is the
