How do I debug glusterfs?

Client-Side Debugging methods

You can add the-o log-level=debug parameter to view detailed debugging information.

Usage examples:

Mount-t Glusterfs-o Log-level=debug 192.168.1.120:/tank/mnt

Server-Side debugging methods

You can change the log level:

Diagnostics.brick-log-level # Brick process log level, default to info

diagnostics.client-log-level # Client log level, default to info

Diagnostics.brick-sys-log-level # Default value is CRITICAL, do not move, in the Gluster log also has

Diagnostics.client-sys-log-level # Default value is CRITICAL, do not move, in the Gluster log also has

Usage examples:

Gluster Volume set Diagnostics.brick-log-level DEBUG

The default startup process for the Glusterd service is:

/usr/sbin/glusterd-p/var/run/glusterd.pid

When debugging, you can reduce the log level:

Glusterd-p/var/run/glusterd.pid-l DEBUG

The optional log levels are:

DEBUG, INFO, WARNING, ERROR, CRITICAL, TRACE and NONE, default is info.

This article is from the "Members Doukua" blog, make sure to keep this source http://dangzhiqiang.blog.51cto.com/7961271/1774433

How do I debug glusterfs?