search for: gf_log

Hi, Fist of all thanks for all the work you put into gluster this product is fantastic. In our setup, we have to have some kind of nfs authentication. Not beeing able to set the rpc-auth option using the cli was a big draw-back for us. Setting the option auth.allow only set the gluster auth.addr.allow option in the bricks themselves but did not do any good regarding nfs access. Setting the

...t chain [2011-04-07 11:29:05.101254] T [rpc-clnt.c:405:rpc_clnt_reconnect] 1-client1: breaking reconnect chain [2011-04-07 11:29:05.101307] T [rpc-clnt.c:405:rpc_clnt_reconnect] 1-client2: breaking reconnect chain Apparently, there are two graphs in the system.(glusterFS 3.1.3 output graph id in gf_log function). My understanding is that there should only be 1 graph which is consist of xlators configured in the .vol file. Due to the HUP signal, the GlusterFS set up a new graph and initialize new TCP connections, so that i got the result above. My question is why there need to be two graphs or mor...

Hi all, Gluster and Ganesha are amazing. Thank you for this great work! I?m struggling with one issue and I think that you might be able to help me. I spent some time by playing with Gluster and Ganesha and after I gain some experience I decided that I should go into production but I?m still struggling with one issue. I have 3x node CentOS 7.3 with the most current Gluster and Ganesha from

...r: frame size (168) > max (-2147458000) Speaking in the IRC channel, Anand Babu (aka rooty) had reason to suspect the following segment of code: > [2008-08-24 18:28] <rooty> if (max_block_size && (blk->size > max_block_size)) { > [2008-08-24 18:28] <rooty> gf_log (trans->xl->name, GF_LOG_ERROR, > [2008-08-24 18:28] <rooty> "frame size (%"PRId32") > max (%"PRId32")", > [2008-08-24 18:28] <rooty> blk->size, max_block_size); > [2008-08-24 18:28] <rooty> /* block si...

Hi, I got the same problem as Juergen, My volume is a simple replicated volume with 2 host and GlusterFS 3.2.0 Volume Name: poolsave Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: ylal2950:/soft/gluster-data Brick2: ylal2960:/soft/gluster-data Options Reconfigured: diagnostics.brick-log-level: DEBUG network.ping-timeout: 20 performance.cache-size: 512MB