Steps to Debug Motr

Check if the bug is known to avoid duplication

Search for existing issue in JIRA.
Do a text search of symptoms, something like, Error log messages or some critical content of stack, etc.

Issue Summary

Write a Crisp summary in JIRA.
For example “Panic found in sd_check() during m0t1fs_rconfc_fail_test.sh run” Try to fit in one sentence.

Issue Description

Explain the Steps and Symptoms here.
State useful facts which you think will be useful for dev to debug issue.
Provide details, to minimize developer requests.
Be very precise.
Provide your TC console output.

Check if there is crash found if yes attach the backtrace here.

1. Goto /var/crash
2. Attach the gdb to your core [> gdb core_name ]
3. Collect the backtrace[ enter bt in gdb prompt ]

Environment

Mention the configuration in issue details.
Mention the build details
Mention if it can be immediately shared with the developer, if the issue is critical.
Mention whether it is Physical Or Virtual Node.
Mention Number of Nodes in cluster.
Menton Numbers of Cores(cpuinfo) in each Nodes.
Mention Number of disks and its utilization[fdisk -l output]

Log files

Execute “motr/utils/m0reportbug --a -b” to collect the m0reportbug-data.tar.xz m0reportbug-traces.tar.xz m0reportbug-cores.tar.xz files.
Attach the following or store on a shared location.
Share the location of log files.

Recreation

Once you hit the issue, please try to recreate in-case it is reproducible and mention same in bug If the bug is not reproducible every time, mention the frequency.
Include the minimum number of steps required to reproduce.
Please make sure the recreation steps followed are mentioned correctly and no step is missing.