[fio.git] / REPORTING-BUGS

Reporting a bug
---------------

If you notice anything that seems like a fio bug, please do send email
to the list (fio@vger.kernel.org, see README) about it. If you are not
running the newest release of fio, upgrading first is recommended.

When reporting a bug, you'll need to include:

1) A description of what you think the bug is
2) Environment (Linux distro version, kernel version). This is mostly
   needed if it's a build bug.
3) The output from fio --version.
4) How to reproduce. Please include a full list of the parameters
   passed to fio and the job file used (if any).

A bug report can't have too much information. Any time information that
is left out and has to be asked for will add to the turn-around time
of getting to the bottom of the issue, and an eventual fix.

That's it!
Commit	Line	Data
	1	Reporting a bug
	2	---------------
	3
	4	If you notice anything that seems like a fio bug, please do send email
	5	to the list (fio@vger.kernel.org, see README) about it. If you are not
	6	running the newest release of fio, upgrading first is recommended.
	7
	8	When reporting a bug, you'll need to include:
	9
	10	1) A description of what you think the bug is
	11	2) Environment (Linux distro version, kernel version). This is mostly
	12	needed if it's a build bug.
	13	3) The output from fio --version.
	14	4) How to reproduce. Please include a full list of the parameters
	15	passed to fio and the job file used (if any).
	16
	17	A bug report can't have too much information. Any time information that
	18	is left out and has to be asked for will add to the turn-around time
	19	of getting to the bottom of the issue, and an eventual fix.
	20
	21	That's it!