From GlusterDocumentation

Contents 1 How to report a bug in GlusterFS 1.1 General instructions 1.2 Spec files 1.3 Log files 1.4 Backtrace 1.5 Reproducing the bug 1.6 Other information

How to report a bug in GlusterFS

If you encounter a bug in GlusterFS, please follow the below guidelines when you report it to the mailing list. Be sure to report it! User feedback is crucial to the health of the project and we value it highly.

General instructions

When running GlusterFS in a non-production environment, be sure to build it with the following command:

 $ make CFLAGS='-g -O0 -DDEBUG'

This includes debugging information which will be helpful in getting backtraces (see below) and also disable optimization. Enabling optimization can result in incorrect line numbers being reported to gdb.

Spec files

Attach all relevant server and client spec files you were using when you encountered the bug. Also tell us details of your setup, i.e., how many clients and how many servers.

Log files

Set the loglevel of your client and server programs to DEBUG (by passing the -L DEBUG option) and attach the log files with your bug report. Obviously, if only the client is failing (for example), you only need to send us the client log file.

Backtrace

If GlusterFS has encountered a segmentation fault or has crashed for some other reason, include the backtrace with the bug report. You can get the backtrace using the following procedure.

Run the GlusterFS client or server inside gdb.

 $ gdb ./glusterfs
 (gdb) set args -f client.spec -N -l/path/to/log/file -LDEBUG /mnt/point
 (gdb) run

Now when the process segfaults, you can get the backtrace by typing:

 (gdb) bt

If the GlusterFS process has crashed and dumped a core file (you can find this in / if running as a daemon and in the current directory otherwise), you can do:

 $ gdb /path/to/glusterfs /path/to/core.<pid>

and then get the backtrace.

If the GlusterFS server or client seems to be hung, then you can get the backtrace by attaching gdb to the process. First get the PID of the process (using ps), and then do:

 $ gdb ./glusterfs <pid>

Press Ctrl-C to interrupt the process and then generate the backtrace.

Reproducing the bug

If the bug is reproducible, please include the steps necessary to do so. If the bug is not reproducible, send us the bug report anyway.

Other information

If you think it is relevant, send us also the version of FUSE you're using, the kernel version, platform (currently Linux only, but send us the name of your distribution).

Thank you for reading this, and once again, your efforts are very much appreciated.