Hi Amar,<br><br># gluster volume set help | grep log<br>Option: diagnostics.brick-log-level<br>Description: Changes the log-level of the bricks<br>Option: diagnostics.client-log-level<br>Description: Changes the log-level of the clients<br>
Option: diagnostics.brick-sys-log-level<br>Description: Gluster's syslog log-level<br>Option: diagnostics.client-sys-log-level<br>Description: Gluster's syslog log-level<br>Description: On an UNSTABLE write from client, return STABLE flag to force client to not send a COMMIT request. In some environments, combined with a replicated GlusterFS setup, this option can improve write performance. This flag allows user to trust Gluster replication logic to sync data to the disks and recover when required. COMMIT requests if received will be handled in a default manner by fsyncing. STABLE writes are still handled in a sync manner. Off by default.<br>
<br><br><br><br><div class="gmail_quote">On Fri, Jun 22, 2012 at 2:41 PM, Amar Tumballi <span dir="ltr"><<a href="mailto:amarts@redhat.com" target="_blank">amarts@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 06/20/2012 04:18 PM, Philippe Muller wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi GlusterFS users,<br>
<br>
I'm looking for the proper way to manage GlusterFS 3.3 logs.<br>
<br>
First, I'd like to centralize all logs coming from GlusterFS. I read<br>
posts mentioning syslog support in this mailing-list archives. I tried a<br>
few volume options like "sys-log-level" or<br>
"[client|brick].syslog-level", but the gluster cli command says these<br>
options doesn't exist.<br>
<br>
</blockquote>
<br></div>
Can you try "gluster volume set help | grep log" ??<br>
<br>
Regards,<br>
Amar<br>
</blockquote></div><br>