Shulou(Shulou.com)06/01 Report--

How to debug GlusterFS, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

Client debugging method

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

Usage example:

Mount-t glusterfs-o log-level=DEBUG 192.168.1.120:/tank / mnt

Server-side debugging method

You can change the log level:

Diagnostics.brick-log-level # brick process log level, default is INFO

Diagnostics.client-log-level # client log level, default is INFO

Diagnostics.brick-sys-log-level # defaults to CRITICAL and does not need to be moved. It is also available in gluster logs.

Diagnostics.client-sys-log-level # defaults to CRITICAL and does not need to be moved. It is also available in gluster logs.

Usage example:

Gluster volume set diagnostics.brick-log-level DEBUG

The default startup process for glusterd service is:

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

When debugging, you can lower 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.

After reading the above, have you mastered how to debug GlusterFS? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.