search for: afr_set_root_inode_on_first_lookup

...9.668234] I [client-handshake.c:453:client_set_lk_version_cbk] 0-share-client-6: Server lk version = 1 [2012-06-21 19:24:39.668287] I [fuse-bridge.c:3376:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13 kernel 7.18 [2012-06-21 19:24:39.668739] I [afr-common.c:1964:afr_set_root_inode_on_first_lookup] 0-share-replicate-0: added root inode [2012-06-21 19:24:39.669232] I [afr-common.c:1964:afr_set_root_inode_on_first_lookup] 0-share-replicate-1: added root inode [2012-06-21 19:24:39.669321] I [afr-common.c:1964:afr_set_root_inode_on_first_lookup] 0-share-replicate-2: added root inode [2012-0...

...o remote volume '/local'. [2012-01-04 20:06:45.327269] I [fuse-bridge.c:3339:fuse_graph_setup] 0-fuse: switched to graph 0 [2012-01-04 20:06:45.327438] E [fuse-bridge.c:2930:fuse_init] 0-glusterfs-fuse: FUSE init failed (Invalid argument) [2012-01-04 20:06:45.328275] I [afr-common.c:1520:afr_set_root_inode_on_first_lookup] 0-test-volume-replicate-0: added root inode [2012-01-04 20:06:45.328767] I [afr-common.c:1520:afr_set_root_inode_on_first_lookup] 0-test-volume-replicate-1: added root inode [2012-01-04 20:06:45.328859] I [fuse-bridge.c:3241:fuse_thread_proc] 0-fuse: unmounting gluster/ [2012-01-04 20:06:45.32...

...eps. [2012-01-24 20:57:22.765190] I [fuse-bridge.c:3339:fuse_graph_setup] 0-fuse: switched to graph 0 [2012-01-24 20:57:22.765314] I [fuse-bridge.c:2927:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13 kernel 7.13 [2012-01-24 20:57:22.765710] I [afr-common.c:1520:afr_set_root_inode_on_first_lookup] 0-openfire-replicate-0: added root inode [2012-01-24 22:15:44.984871] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-openfire-client-0: remote operation failed: Stale NFS file handle [2012-01-24 22:15:44.985228] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-openfire-client-1: remote oper...

HI: I run glusterfs with four nodes, 2x2 Distributed-Replicate. I mounted it via fuse and did some test, it was ok. However when I mounted it via nfs, a problem was found: When I copied 200G files to the glusterfs, the glusterfs process in the server node(mounted by client) was killed because of OOM, and all terminals of the client were hung. Trying to test for many times, I got the

We brought up a test cluster to investigate GlusterFS. Using the Quick Start instructions, we brought up a 2 server 1 brick replicating setup and mounted to it from a third box with the fuse mount (all ver 3.4.1) # gluster volume info Volume Name: mailtest Type: Replicate Volume ID: 9e412774-b8c9-4135-b7fb-bc0dd298d06a Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks:

Hi, I've got Gluster error: Transport endpoint not connected. It came up twice after trying to rsync 2 TB filesystem over; it reached about 1.8 TB and got the error. Logs on the server side (on reverse time order): [2012-12-15 00:53:24.747934] I [server-helpers.c:629:server_connection_destroy] 0-RedhawkShared-server: destroyed connection of

Hi, I'm using Gluster 3.3.0-1.el6.x86_64, on two storage nodes, replicated mode (fs1, fs2) Node specs: CentOS 6.2 Intel Quad Core 2.8Ghz, 4Gb ram, 3ware raid, 2x500GB sata 7200rpm (RAID1 for os), 6x1TB sata 7200rpm (RAID10 for /data), 1Gbit network I've it mounted data partition to web1 a Dual Quad 2.8Ghz, 8Gb ram, using glusterfs. (also tried NFS -> Gluster mount) We have 50Gb of