Re: [Gluster-users] SETVOLUME failed
Hi, Is the volume spec file (by default it will be /etc/glusterfs/glusterfs.vol) same on all the servers? If not, delete the file from servers, which are not volfile-servers (other than 192.168.1.1 here) or make sure you have the same file on all the servers. regards, On Mon, Jan 11, 2010 at 7:06 PM, wrote: > > Hi all, > > I have glusterFS at version 3.0.0 on debian testing and I have this > problem: > > [2010-01-11 15:58:45] W [socket.c:1407:socket_init] trans: disabling > non-blocking IO > [2010-01-11 15:58:45] W [socket.c:1407:socket_init] trans: disabling > non-blocking IO > > > Version : glusterfs 3.0.0 built on Dec 9 2009 12:15:42 > git: 2.0.1-886-g8379edd > Starting Time: 2010-01-11 15:58:45 > Command line : /usr/sbin/glusterfs --volfile-server=192.168.2.11 /mnt/ > PID : 3070 > System name : Linux > Nodename : B125-GMHI-XXX > Kernel Release : 2.6.31-14-generic > Hardware Identifier: i686 > > Given volfile: > > +--+ > 1: # RAID 1 > 2: # TRANSPORT-TYPE tcp > 3: volume prema-1 > 4: type protocol/client > 5: option transport-type tcp > 6: option remote-host prema > 7: option transport.socket.nodelay on > 8: option remote-port 6996 > 9: option remote-subvolume brick > 10: end-volume > 11: > 12: volume britain-1 > 13: type protocol/client > 14: option transport-type tcp > 15: option remote-host britain > 16: option transport.socket.nodelay on > 17: option remote-port 6996 > 18: option remote-subvolume brick > 19: end-volume > 20: > 21: volume mirror-0 > 22: type cluster/replicate > 23: subvolumes britain-1 prema-1 > 24: end-volume > 25: > 26: volume writebehind > 27: type performance/write-behind > 28: option cache-size 4MB > 29: subvolumes mirror-0 > 30: end-volume > 31: > 32: volume readahead > 33: type performance/read-ahead > 34: option page-count 4 > 35: subvolumes writebehind > 36: end-volume > 37: > 38: volume iocache > 39: type performance/io-cache > 40: option cache-size 1GB > 41: option cache-timeout 1 > 42: subvolumes readahead > 43: end-volume > 44: > 45: volume quickread > 46: type performance/quick-read > 47: option cache-timeout 1 > 48: option max-file-size 64kB > 49: subvolumes iocache > 50: end-volume > 51: > 52: volume statprefetch > 53: type performance/stat-prefetch > 54: subvolumes quickread > 55: end-volume > 56: > > > +--+ > [2010-01-11 15:58:45] N [glusterfsd.c:1361:main] glusterfs: Successfully > started > [2010-01-11 15:58:45] N [client-protocol.c:6224:client_setvolume_cbk] > britain-1: Connected to 192.168.2.11:6996, attached to remote volume > 'brick'. > [2010-01-11 15:58:45] N [afr.c:2625:notify] mirror-0: Subvolume 'britain-1' > came back up; going online. > [2010-01-11 15:58:45] N [client-protocol.c:6224:client_setvolume_cbk] > britain-1: Connected to 192.168.2.11:6996, attached to remote volume > 'brick'. > [2010-01-11 15:58:45] N [afr.c:2625:notify] mirror-0: Subvolume 'britain-1' > came back up; going online. > [2010-01-11 15:58:45] E [client-protocol.c:6187:client_setvolume_cbk] > prema-1: SETVOLUME on remote-host failed: volume-file checksum varies from > earlier access > [2010-01-11 15:58:45] C [fuse-bridge.c:3300:notify] fuse: Remote volume > file changed, try re-mounting. > [2010-01-11 15:58:45] W [glusterfsd.c:928:cleanup_and_exit] glusterfs: > shutting down > [2010-01-11 15:58:45] N [fuse-bridge.c:3519:fini] fuse: Unmounting '/mnt/'. > [2010-01-11 15:58:45] N [fuse-bridge.c:3119:fuse_thread_proc] > glusterfs-fuse: terminating upon getting EBADF when reading /dev/fuse > [2010-01-11 15:58:45] W [glusterfsd.c:928:cleanup_and_exit] glusterfs: > shutting down > > But if I do it this way "mount -t glusterfs /etc/glusterfs/glusterfs.vol > /mnt/"(with the same glusterfs.vol settings) it works correctly. I dont know > where is the problem. Do anyone know? > > > This message was sent using IMP, the Internet Messaging Program. > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > -- Raghavendra G ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] booster with apache permission denied
Oh, sorry, here are the glusterfsd server logs - this is all it logged from the Apache startup and wget. server1: [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1014 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1015 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1010 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1011 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1006 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1007 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1002 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1005 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1001 [2010-01-11 22:09:39] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1004 [2010-01-11 22:09:49] E [posix.c:270:posix_lookup] server1: lstat on /data/tnsc/test/test.mp3/.htaccess failed: Not a directory server2: [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1017 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:1016 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:993 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:992 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:987 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:984 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:983 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:981 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:982 [2010-01-11 22:14:12] N [server-protocol.c:7056:mop_setvolume] server: accepted client from 192.168.12.72:980 [2010-01-11 22:14:14] E [posix.c:270:posix_lookup] server2: lstat on /data/tnsc/test/test.mp3/.htaccess failed: Not a directory thanks, liam On Mon, Jan 11, 2010 at 9:42 PM, Raghavendra G wrote: > Hi, > > Can you send the glusterfs server logs? The logs you've sent are of booster > (which is glusterfs client). Looking at the configuration, there is a > protocol/client in configuration and hence you need a glusterfs server > running. > > We'll work on issue of md5sums being different. > > regards, > On Tue, Jan 12, 2010 at 2:20 AM, Liam Slusser wrote: >> >> Logs are below. I also noticed this while trying to debug this >> issue...Notice the md5sum do not match up below? >> >> On the fuse mounted system: >> >> [r...@server test]# ls -al test.mp3 >> -rw-r--r-- 1 user group 3692251 Aug 27 2007 test.mp3 >> >> [r...@server test]# md5sum test.mp3 >> d480d794882c814ae1a2426b79cf8b3e test.mp3 >> >> Using glusterfs-boost.so: >> >> [r...@server tmp]# >> >> LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" >> ls -al /pub/data/tnsc/test/test.mp3 >> ls: /pub/data/tnsc/test/test.mp3: Invalid argument >> -rw-r--r-- 1 tcode tcode 3692251 Aug 27 2007 /pub/data/tnsc/test/test.mp3 >> >> [r...@server tmp]# >> >> LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" >> cp /pub/data/tnsc/test/test.mp3 /tmp/test.mp3 >> >> [r...@server tmp]# md5sum /tmp/test.mp3 >> 9bff3bb90b6897fc19b6b4658b83f3f8 /tmp/test.mp3 >> >> [r...@server tmp]# ls -al /tmp/test.mp3 >> -rw-r--r-- 1 root root 3690496 Jan 11 14:10 /tmp/test.mp3 >> >> Here are the gluster logs from a clean apache start and one request to >> test.mp3 with wget: >> >> [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: >> dlsym(notify) on >> >> /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-threads.so: >> undefined symbol: notify -- neglecting >> [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: >> dlsym(notify) on >> >> /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/read-ahead.so: >> undefined symbol: notify -- neglecting >> [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: >> dlsym(notify) on >> >> /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-cache.so: >> undefined symbol: notify -- neglecting >> [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick1a: >> defaulting frame-timeout to 30mins >> [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick1a: >> d
Re: [Gluster-users] booster with apache permission denied
Hi, Can you send the glusterfs server logs? The logs you've sent are of booster (which is glusterfs client). Looking at the configuration, there is a protocol/client in configuration and hence you need a glusterfs server running. We'll work on issue of md5sums being different. regards, On Tue, Jan 12, 2010 at 2:20 AM, Liam Slusser wrote: > Logs are below. I also noticed this while trying to debug this > issue...Notice the md5sum do not match up below? > > On the fuse mounted system: > > [r...@server test]# ls -al test.mp3 > -rw-r--r-- 1 user group 3692251 Aug 27 2007 test.mp3 > > [r...@server test]# md5sum test.mp3 > d480d794882c814ae1a2426b79cf8b3e test.mp3 > > Using glusterfs-boost.so: > > [r...@server tmp]# > > LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" > ls -al /pub/data/tnsc/test/test.mp3 > ls: /pub/data/tnsc/test/test.mp3: Invalid argument > -rw-r--r-- 1 tcode tcode 3692251 Aug 27 2007 /pub/data/tnsc/test/test.mp3 > > [r...@server tmp]# > > LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" > cp /pub/data/tnsc/test/test.mp3 /tmp/test.mp3 > > [r...@server tmp]# md5sum /tmp/test.mp3 > 9bff3bb90b6897fc19b6b4658b83f3f8 /tmp/test.mp3 > > [r...@server tmp]# ls -al /tmp/test.mp3 > -rw-r--r-- 1 root root 3690496 Jan 11 14:10 /tmp/test.mp3 > > Here are the gluster logs from a clean apache start and one request to > test.mp3 with wget: > > [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: > dlsym(notify) on > > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-threads.so: > undefined symbol: notify -- neglecting > [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: > dlsym(notify) on > > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/read-ahead.so: > undefined symbol: notify -- neglecting > [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: > dlsym(notify) on > > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-cache.so: > undefined symbol: notify -- neglecting > [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick1a: > defaulting frame-timeout to 30mins > [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick1a: > defaulting ping-timeout to 10 > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick2a: > defaulting frame-timeout to 30mins > [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick2a: > defaulting ping-timeout to 10 > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [io-threads.c:2280:init] iothreads: > io-threads: Autoscaling: off, min_threads: 32, max_threads: 32 > [2010-01-11 14:16:02] D [read-ahead.c:824:init] readahead: Using > conf->page_count = 16 > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick2a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick1a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick1a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick2a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] N [client-protocol.c:5733:client_setvolume_cbk] > brick1a: Connected to 192.168.12.30:6996, attached to remote volume > 'brick1a'. > [2010-01-11 14:16:02] N [afr.c:2194:notify] replicate: Subvolume > 'brick1a' came back up; g
Re: [Gluster-users] booster with apache permission denied
I was able to install lighttpd 1.4.25 and it appears to work just fine with glusterfs-booster.so. So I think its an issue with Apache 2.2.14 (the newest version available). I suppose i can try an older version of Apache and see if i have better luck (say 2.0)... liam On Mon, Jan 11, 2010 at 2:20 PM, Liam Slusser wrote: > Logs are below. I also noticed this while trying to debug this > issue...Notice the md5sum do not match up below? > > On the fuse mounted system: > > [r...@server test]# ls -al test.mp3 > -rw-r--r-- 1 user group 3692251 Aug 27 2007 test.mp3 > > [r...@server test]# md5sum test.mp3 > d480d794882c814ae1a2426b79cf8b3e test.mp3 > > Using glusterfs-boost.so: > > [r...@server tmp]# > LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" > ls -al /pub/data/tnsc/test/test.mp3 > ls: /pub/data/tnsc/test/test.mp3: Invalid argument > -rw-r--r-- 1 tcode tcode 3692251 Aug 27 2007 /pub/data/tnsc/test/test.mp3 > > [r...@server tmp]# > LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" > cp /pub/data/tnsc/test/test.mp3 /tmp/test.mp3 > > [r...@server tmp]# md5sum /tmp/test.mp3 > 9bff3bb90b6897fc19b6b4658b83f3f8 /tmp/test.mp3 > > [r...@server tmp]# ls -al /tmp/test.mp3 > -rw-r--r-- 1 root root 3690496 Jan 11 14:10 /tmp/test.mp3 > > Here are the gluster logs from a clean apache start and one request to > test.mp3 with wget: > > [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: > dlsym(notify) on > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-threads.so: > undefined symbol: notify -- neglecting > [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: > dlsym(notify) on > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/read-ahead.so: > undefined symbol: notify -- neglecting > [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: > dlsym(notify) on > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-cache.so: > undefined symbol: notify -- neglecting > [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick1a: > defaulting frame-timeout to 30mins > [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick1a: > defaulting ping-timeout to 10 > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick2a: > defaulting frame-timeout to 30mins > [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick2a: > defaulting ping-timeout to 10 > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: > attempt to load file > /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so > [2010-01-11 14:16:02] D [io-threads.c:2280:init] iothreads: > io-threads: Autoscaling: off, min_threads: 32, max_threads: 32 > [2010-01-11 14:16:02] D [read-ahead.c:824:init] readahead: Using > conf->page_count = 16 > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got > GF_EVENT_PARENT_UP, attempting connect on transport > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick2a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick1a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick1a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick2a: got > GF_EVENT_CHILD_UP > [2010-01-11 14:16:02] N [client-protocol.c:5733:client_setvolume_cbk] > brick1a: Connected to 192.168.12.30:6996, attached to remote volume > 'brick1a'. > [2010-01-11 14:16:02] N [afr.c:2194:notify] replicate: Subvolume > 'brick1a' came back up; going online. > [2010-01-11 14
Re: [Gluster-users] booster with apache permission denied
Logs are below. I also noticed this while trying to debug this issue...Notice the md5sum do not match up below? On the fuse mounted system: [r...@server test]# ls -al test.mp3 -rw-r--r-- 1 user group 3692251 Aug 27 2007 test.mp3 [r...@server test]# md5sum test.mp3 d480d794882c814ae1a2426b79cf8b3e test.mp3 Using glusterfs-boost.so: [r...@server tmp]# LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" ls -al /pub/data/tnsc/test/test.mp3 ls: /pub/data/tnsc/test/test.mp3: Invalid argument -rw-r--r-- 1 tcode tcode 3692251 Aug 27 2007 /pub/data/tnsc/test/test.mp3 [r...@server tmp]# LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" cp /pub/data/tnsc/test/test.mp3 /tmp/test.mp3 [r...@server tmp]# md5sum /tmp/test.mp3 9bff3bb90b6897fc19b6b4658b83f3f8 /tmp/test.mp3 [r...@server tmp]# ls -al /tmp/test.mp3 -rw-r--r-- 1 root root 3690496 Jan 11 14:10 /tmp/test.mp3 Here are the gluster logs from a clean apache start and one request to test.mp3 with wget: [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-threads.so: undefined symbol: notify -- neglecting [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/read-ahead.so: undefined symbol: notify -- neglecting [2010-01-11 14:16:02] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/xlator/performance/io-cache.so: undefined symbol: notify -- neglecting [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick1a: defaulting frame-timeout to 30mins [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick1a: defaulting ping-timeout to 10 [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: attempt to load file /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: attempt to load file /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so [2010-01-11 14:16:02] D [client-protocol.c:6130:init] brick2a: defaulting frame-timeout to 30mins [2010-01-11 14:16:02] D [client-protocol.c:6141:init] brick2a: defaulting ping-timeout to 10 [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: attempt to load file /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so [2010-01-11 14:16:02] D [transport.c:141:transport_load] transport: attempt to load file /home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/2.0.9/transport/socket.so [2010-01-11 14:16:02] D [io-threads.c:2280:init] iothreads: io-threads: Autoscaling: off, min_threads: 32, max_threads: 32 [2010-01-11 14:16:02] D [read-ahead.c:824:init] readahead: Using conf->page_count = 16 [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick1a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6472:notify] brick2a: got GF_EVENT_PARENT_UP, attempting connect on transport [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick2a: got GF_EVENT_CHILD_UP [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick1a: got GF_EVENT_CHILD_UP [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick1a: got GF_EVENT_CHILD_UP [2010-01-11 14:16:02] D [client-protocol.c:6486:notify] brick2a: got GF_EVENT_CHILD_UP [2010-01-11 14:16:02] N [client-protocol.c:5733:client_setvolume_cbk] brick1a: Connected to 192.168.12.30:6996, attached to remote volume 'brick1a'. [2010-01-11 14:16:02] N [afr.c:2194:notify] replicate: Subvolume 'brick1a' came back up; going online. [2010-01-11 14:16:02] N [client-protocol.c:5733:client_setvolume_cbk] brick1a: Connected to 192.168.12.30:6996, attached to remote volume 'brick1a'. [2010-01-11 14:16:02] N [afr.c:2194:notify] replicate: Subvolume 'brick1a' came back up; going online. [2010-01-11 14:16:02] N [client-protocol.c:5733:client_setvolume_cbk] brick2a: Connected to 192.168.12.35:6996, attached to remote volume 'brick2a'. [2010-01-11 14:16:02] N [client-protocol.c:5733:client_setvolume_cbk] brick2a: Connected to 192.168.12.35:6996, attached to r
Re: [Gluster-users] booster with apache permission denied
2010/1/12 Raghavendra G > Hi Liam, > > Can you send glusterfs server logs? > > regards, > On Sat, Jan 9, 2010 at 1:46 AM, Liam Slusser wrote: > >> I believe i posted this here before but never got any replies. I'm in >> the middle of upgrading to Gluster 2.0.9 and would like to move away >> from having to use fuse to serve up files out of apache so im working >> again on getting boosting working correctly. >> >> Everything appears to load and work fine but i always get permission >> denied, 403, in my apache logs. Works fine under fuse. I'm running >> Apache under the user nobody which does have read access to all the >> files. >> >> I'm not sure where to start debugging this? Ideas? >> >> thanks, >> liam >> >> I can run things from the command line... >> >> [r...@server]# >> LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" >> file /pub/data/tnsc/test/test.mp3 >> /pub/data/tnsc/test/test.mp3: MPEG ADTS, layer III, v1, 128 kBits, >> 44.1 kHz, JntStereo >> >> [r...@server]# >> LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" >> ls -agl /pub/data/tnsc/test/test.mp3 >> ls: /pub/data/tnsc/test/test.mp3: Invalid argument >> -rw-r--r-- 1 user 3692251 Aug 27 2007 /pub/data/tnsc/test/test.mp3 >> >> [r...@server]# wget -S http://x.x.x.x/tnsc/test/test.mp3 >> --2010-01-08 13:34:55-- http://x.x.x.x/tnsc/test/test.mp3 >> Connecting to x.x.x.x:80... connected. >> HTTP request sent, awaiting response... >> HTTP/1.1 403 Forbidden >> Date: Fri, 08 Jan 2010 21:34:55 GMT >> Server: Apache/2.2.14 (Unix) >> Content-Length: 228 >> Keep-Alive: timeout=5, max=100 >> Connection: Keep-Alive >> Content-Type: text/html; charset=iso-8859-1 >> 2010-01-08 13:34:55 ERROR 403: Forbidden. >> >> Apache access log: >> >> x.x.x.x - - [08/Jan/2010:12:50:46 -0800] "GET /tnsc/test/test.mp3 >> HTTP/1.0" 403 228 "-" "Wget/1.11.4 Red Hat modified" >> >> Apache error log: >> >> [Fri Jan 08 12:50:46 2010] [error] [client x..x.x.x] (22)Invalid >> argument: file permissions deny server access: >> /pub/data/tnsc/test/test.mp3 >> >> Gluster error log: >> >> [2010-01-08 12:50:46] D [libglusterfsclient.c:4866:glusterfs_stat] >> libglusterfsclient: path /pub/data/tnsc/test/test.mp3 >> [2010-01-08 12:50:46] D >> [libglusterfsclient.c:1541:_libgf_vmp_search_entry] >> libglusterfsclient: VMP Search: path /pub/data/tnsc/test/test.mp3, >> type: LongestPrefix >> [2010-01-08 12:50:46] D >> [libglusterfsclient.c:1628:libgf_vmp_search_entry] libglusterfsclient: >> VMP Entry found: path :/pub/data/tnsc/test/test.mp3 vmp: /pub/ >> [2010-01-08 12:50:46] D [libglusterfsclient.c:4788:__glusterfs_stat] >> libglusterfsclient: path /data/tnsc/test/test.mp3, op: 2 >> [2010-01-08 12:50:46] D >> [libglusterfsclient.c:869:libgf_resolve_path_light] >> libglusterfsclient: Path: /data/tnsc/test/test.mp3, Resolved Path: >> /data/tnsc/test/test.mp3 >> [2010-01-08 12:50:46] D >> [libglusterfsclient-dentry.c:389:libgf_client_path_lookup] >> libglusterfsclient: resolved path(/data/tnsc/test/test.mp3) to >> 1118653312/1118655564 >> [2010-01-08 12:50:46] D [libglusterfsclient.c:4710:libgf_client_stat] >> libglusterfsclient: Cache will be used >> [2010-01-08 12:50:46] D [libglusterfsclient.c:3001:glusterfs_open] >> libglusterfsclient: path /pub/data/tnsc/test/test.mp3 >> [2010-01-08 12:50:46] D >> [libglusterfsclient.c:1541:_libgf_vmp_search_entry] >> libglusterfsclient: VMP Search: path /pub/data/tnsc/test/test.mp3, >> type: LongestPrefix >> [2010-01-08 12:50:46] D >> [libglusterfsclient.c:1628:libgf_vmp_search_entry] libglusterfsclient: >> VMP Entry found: path :/pub/data/tnsc/test/test.mp3 vmp: /pub/ >> [2010-01-08 12:50:46] D >> [libglusterfsclient.c:869:libgf_resolve_path_light] >> libglusterfsclient: Path: /data/tnsc/test/test.mp3, Resolved Path: >> /data/tnsc/test/test.mp3 >> [2010-01-08 12:50:46] D >> [libglusterfsclient-dentry.c:389:libgf_client_path_lookup] >> libglusterfsclient: resolved path(/data/tnsc/test/test.mp3) to >> 1118653312/1118655564 >> [2010-01-08 12:50:46] D [libglusterfsclient.c:2752:libgf_client_open] >> libglusterfsclient: open: path /data/tnsc/test/test.mp3, status: 0, >> errno 117 >> >> Booster.fstab: >> >> /home/gluster/apps/glusterfs-2.0.9/etc/glusterfs/glusterfs.vol-pub.booster >> /pub/ glusterfs >> >> subvolume=cache,logfile=/home/gluster/apps/glusterfs-2.0.9/var/log/glusterfs/booster-pub.log,loglevel=DEBUG,attr_timeout=0 >> >> glusterfs.vol-pub.booster: >> >> volume brick1a >> type protocol/client >> option transport-type tcp >> option remote-host x.x.x.30 >> option remote-subvolume brick1a >> end-volume >> >> volume brick2a >> type protocol/client >> option transport-type tcp >> option remote-host x.x.x.35 >> option remote-subvolume brick2a >> end-volume >> >> volume replicate >> type cluster/replicate >> subvolumes brick1a brick2a >> end-volume >> >> volume iothreads >> type performance/io-threads >> option thread-count 32 >> subvolumes replicate >> end-vol
Re: [Gluster-users] booster with apache permission denied
Hi Liam, Can you send glusterfs server logs? regards, On Sat, Jan 9, 2010 at 1:46 AM, Liam Slusser wrote: > I believe i posted this here before but never got any replies. I'm in > the middle of upgrading to Gluster 2.0.9 and would like to move away > from having to use fuse to serve up files out of apache so im working > again on getting boosting working correctly. > > Everything appears to load and work fine but i always get permission > denied, 403, in my apache logs. Works fine under fuse. I'm running > Apache under the user nobody which does have read access to all the > files. > > I'm not sure where to start debugging this? Ideas? > > thanks, > liam > > I can run things from the command line... > > [r...@server]# > LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" > file /pub/data/tnsc/test/test.mp3 > /pub/data/tnsc/test/test.mp3: MPEG ADTS, layer III, v1, 128 kBits, > 44.1 kHz, JntStereo > > [r...@server]# > LD_PRELOAD="/home/gluster/apps/glusterfs-2.0.9/lib/glusterfs/glusterfs-booster.so" > ls -agl /pub/data/tnsc/test/test.mp3 > ls: /pub/data/tnsc/test/test.mp3: Invalid argument > -rw-r--r-- 1 user 3692251 Aug 27 2007 /pub/data/tnsc/test/test.mp3 > > [r...@server]# wget -S http://x.x.x.x/tnsc/test/test.mp3 > --2010-01-08 13:34:55-- http://x.x.x.x/tnsc/test/test.mp3 > Connecting to x.x.x.x:80... connected. > HTTP request sent, awaiting response... > HTTP/1.1 403 Forbidden > Date: Fri, 08 Jan 2010 21:34:55 GMT > Server: Apache/2.2.14 (Unix) > Content-Length: 228 > Keep-Alive: timeout=5, max=100 > Connection: Keep-Alive > Content-Type: text/html; charset=iso-8859-1 > 2010-01-08 13:34:55 ERROR 403: Forbidden. > > Apache access log: > > x.x.x.x - - [08/Jan/2010:12:50:46 -0800] "GET /tnsc/test/test.mp3 > HTTP/1.0" 403 228 "-" "Wget/1.11.4 Red Hat modified" > > Apache error log: > > [Fri Jan 08 12:50:46 2010] [error] [client x..x.x.x] (22)Invalid > argument: file permissions deny server access: > /pub/data/tnsc/test/test.mp3 > > Gluster error log: > > [2010-01-08 12:50:46] D [libglusterfsclient.c:4866:glusterfs_stat] > libglusterfsclient: path /pub/data/tnsc/test/test.mp3 > [2010-01-08 12:50:46] D > [libglusterfsclient.c:1541:_libgf_vmp_search_entry] > libglusterfsclient: VMP Search: path /pub/data/tnsc/test/test.mp3, > type: LongestPrefix > [2010-01-08 12:50:46] D > [libglusterfsclient.c:1628:libgf_vmp_search_entry] libglusterfsclient: > VMP Entry found: path :/pub/data/tnsc/test/test.mp3 vmp: /pub/ > [2010-01-08 12:50:46] D [libglusterfsclient.c:4788:__glusterfs_stat] > libglusterfsclient: path /data/tnsc/test/test.mp3, op: 2 > [2010-01-08 12:50:46] D > [libglusterfsclient.c:869:libgf_resolve_path_light] > libglusterfsclient: Path: /data/tnsc/test/test.mp3, Resolved Path: > /data/tnsc/test/test.mp3 > [2010-01-08 12:50:46] D > [libglusterfsclient-dentry.c:389:libgf_client_path_lookup] > libglusterfsclient: resolved path(/data/tnsc/test/test.mp3) to > 1118653312/1118655564 > [2010-01-08 12:50:46] D [libglusterfsclient.c:4710:libgf_client_stat] > libglusterfsclient: Cache will be used > [2010-01-08 12:50:46] D [libglusterfsclient.c:3001:glusterfs_open] > libglusterfsclient: path /pub/data/tnsc/test/test.mp3 > [2010-01-08 12:50:46] D > [libglusterfsclient.c:1541:_libgf_vmp_search_entry] > libglusterfsclient: VMP Search: path /pub/data/tnsc/test/test.mp3, > type: LongestPrefix > [2010-01-08 12:50:46] D > [libglusterfsclient.c:1628:libgf_vmp_search_entry] libglusterfsclient: > VMP Entry found: path :/pub/data/tnsc/test/test.mp3 vmp: /pub/ > [2010-01-08 12:50:46] D > [libglusterfsclient.c:869:libgf_resolve_path_light] > libglusterfsclient: Path: /data/tnsc/test/test.mp3, Resolved Path: > /data/tnsc/test/test.mp3 > [2010-01-08 12:50:46] D > [libglusterfsclient-dentry.c:389:libgf_client_path_lookup] > libglusterfsclient: resolved path(/data/tnsc/test/test.mp3) to > 1118653312/1118655564 > [2010-01-08 12:50:46] D [libglusterfsclient.c:2752:libgf_client_open] > libglusterfsclient: open: path /data/tnsc/test/test.mp3, status: 0, > errno 117 > > Booster.fstab: > > /home/gluster/apps/glusterfs-2.0.9/etc/glusterfs/glusterfs.vol-pub.booster > /pub/ glusterfs > > subvolume=cache,logfile=/home/gluster/apps/glusterfs-2.0.9/var/log/glusterfs/booster-pub.log,loglevel=DEBUG,attr_timeout=0 > > glusterfs.vol-pub.booster: > > volume brick1a > type protocol/client > option transport-type tcp > option remote-host x.x.x.30 > option remote-subvolume brick1a > end-volume > > volume brick2a > type protocol/client > option transport-type tcp > option remote-host x.x.x.35 > option remote-subvolume brick2a > end-volume > > volume replicate > type cluster/replicate > subvolumes brick1a brick2a > end-volume > > volume iothreads > type performance/io-threads > option thread-count 32 > subvolumes replicate > end-volume > > volume readahead > type performance/read-ahead > option page-count 16 # cache per file = (page-count x page-size) > option force-atime-update off >
[Gluster-users] SETVOLUME failed
Hi all, I have glusterFS at version 3.0.0 on debian testing and I have this problem: [2010-01-11 15:58:45] W [socket.c:1407:socket_init] trans: disabling non-blocking IO [2010-01-11 15:58:45] W [socket.c:1407:socket_init] trans: disabling non-blocking IO Version : glusterfs 3.0.0 built on Dec 9 2009 12:15:42 git: 2.0.1-886-g8379edd Starting Time: 2010-01-11 15:58:45 Command line : /usr/sbin/glusterfs --volfile-server=192.168.2.11 /mnt/ PID : 3070 System name : Linux Nodename : B125-GMHI-XXX Kernel Release : 2.6.31-14-generic Hardware Identifier: i686 Given volfile: +--+ 1: # RAID 1 2: # TRANSPORT-TYPE tcp 3: volume prema-1 4: type protocol/client 5: option transport-type tcp 6: option remote-host prema 7: option transport.socket.nodelay on 8: option remote-port 6996 9: option remote-subvolume brick 10: end-volume 11: 12: volume britain-1 13: type protocol/client 14: option transport-type tcp 15: option remote-host britain 16: option transport.socket.nodelay on 17: option remote-port 6996 18: option remote-subvolume brick 19: end-volume 20: 21: volume mirror-0 22: type cluster/replicate 23: subvolumes britain-1 prema-1 24: end-volume 25: 26: volume writebehind 27: type performance/write-behind 28: option cache-size 4MB 29: subvolumes mirror-0 30: end-volume 31: 32: volume readahead 33: type performance/read-ahead 34: option page-count 4 35: subvolumes writebehind 36: end-volume 37: 38: volume iocache 39: type performance/io-cache 40: option cache-size 1GB 41: option cache-timeout 1 42: subvolumes readahead 43: end-volume 44: 45: volume quickread 46: type performance/quick-read 47: option cache-timeout 1 48: option max-file-size 64kB 49: subvolumes iocache 50: end-volume 51: 52: volume statprefetch 53: type performance/stat-prefetch 54: subvolumes quickread 55: end-volume 56: +--+ [2010-01-11 15:58:45] N [glusterfsd.c:1361:main] glusterfs: Successfully started [2010-01-11 15:58:45] N [client-protocol.c:6224:client_setvolume_cbk] britain-1: Connected to 192.168.2.11:6996, attached to remote volume 'brick'. [2010-01-11 15:58:45] N [afr.c:2625:notify] mirror-0: Subvolume 'britain-1' came back up; going online. [2010-01-11 15:58:45] N [client-protocol.c:6224:client_setvolume_cbk] britain-1: Connected to 192.168.2.11:6996, attached to remote volume 'brick'. [2010-01-11 15:58:45] N [afr.c:2625:notify] mirror-0: Subvolume 'britain-1' came back up; going online. [2010-01-11 15:58:45] E [client-protocol.c:6187:client_setvolume_cbk] prema-1: SETVOLUME on remote-host failed: volume-file checksum varies from earlier access [2010-01-11 15:58:45] C [fuse-bridge.c:3300:notify] fuse: Remote volume file changed, try re-mounting. [2010-01-11 15:58:45] W [glusterfsd.c:928:cleanup_and_exit] glusterfs: shutting down [2010-01-11 15:58:45] N [fuse-bridge.c:3519:fini] fuse: Unmounting '/mnt/'. [2010-01-11 15:58:45] N [fuse-bridge.c:3119:fuse_thread_proc] glusterfs-fuse: terminating upon getting EBADF when reading /dev/fuse [2010-01-11 15:58:45] W [glusterfsd.c:928:cleanup_and_exit] glusterfs: shutting down But if I do it this way "mount -t glusterfs /etc/glusterfs/glusterfs.vol /mnt/"(with the same glusterfs.vol settings) it works correctly. I dont know where is the problem. Do anyone know? This message was sent using IMP, the Internet Messaging Program. ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] maxing out cpu
Quick follow up. After checking with Shehjar, I've logged this as a bug report - #530 ( http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=530 ). Cheers Dave On Sat, 2010-01-09 at 10:08 +1100, Dave Hall wrote: > Hi Shehjar, > > On Fri, 2010-01-08 at 13:58 +0530, Shehjar Tikoo wrote: > > The callgrind output can be opened using kcachegrind. See the attd > > png for what I observe here. For some reason, inode_path is consuming > > unusual amount of CPU. > > This is what I saw too. It didn't mean too much to me so I just bzip'd > it and sent it off. > > As I mentioned on IRC, based on a quick look at the code, I suspect it > is all going wrong in libglusterfs/src/inode.c lines 902-908. Sorry I > don't know enough C to be able to do anything to fix it :( > > > This could be a resurfacing of a bug we thought > > was fixed by an earlier patch. Do you still have the logs for this > > particular run? Those are what we need to start looking deeper. > > As we discussed the log just shows gluster starting and outputing some > environment info and the volfile. > > Cheers > > Dave > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Random directory/files gets unavailable after sometime
Hello Vijay, Just want to inform that i applied this fix and glusterfs is working perfectly here for 3 days. Best Regards, --- Fernando Marcelo www.consultorpc.com ferna...@consultorpc.com Em 08/01/2010, às 04:01, Vijay Bellur escreveu: > Hello Fernando, > > Can you please try by applying this patch to GlusterFS v3.0.0? > > http://patches.gluster.com/patch/2622 > > Thanks, > Vijay ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Storage Platform boot hangs on udev
Hi Wim, We never tested with Areca RAID Card, i have recently sent a patch which adds support for the Areca Card. 3.0.1 will be released on Feb 1st week which should include this update. Regards -- Harshavardhana Gluster - http://www.gluster.com On Sun, Jan 10, 2010 at 9:57 PM, wrote: > Hi all > I'm trying a test install of the Gluster Storage Platform 3.0 on a new > server (Intel S5520UR with Areca RAID); > After what appears to be a succesful installation (tried both the USB and > cd release), the box is rebooted, and then > just hangs showing a black screen. > > After removing the 'rhgb quiet' kernel options from grub (having booted > from livecd), the boot process appears to get > stuck at 'Starting udev'. Changing log level in udev.conf to debug or info > does not print out any additional info and > nothing seems to get syslogged. > As suggested by google results on similar problems on FC11 and others, I've > tried booting with different grub > kernel options (like noacpi, nousb, etc) to no avail. The boot process > seems to hang forever and does not timeout. > Also tried to boot with the 2.6.29 kernel that's included, with more or > less the same result; After the 'Starting udev' > line, it does print out some more info about found usb devices (keyboard, > mouse), but after that just hangs like with > the default 2.6.30. > > All suggestions greatly appreciated. > > cheers > Wim > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
