Reporting bugs
From Linux NFS
(Difference between revisions)
Chucklever (Talk | contribs) m (Reverted edits by DviYnz (Talk); changed back to last version by Chucklever) |
m (→Places to report bugs) |
||
| Line 3: | Line 3: | ||
The official place to report bugs or make feature requests is the [http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4 NFSv4 development list], nfsv4 at linux-nfs.org. | The official place to report bugs or make feature requests is the [http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4 NFSv4 development list], nfsv4 at linux-nfs.org. | ||
| - | There is also a [ | + | There is also a [https://bugzilla.linux-nfs.org/ Bugzilla bug tracker] where known bugs are tracked. You probably should review this list before reporting your issue, in case it is already known. |
==Basic information to include in bug reports== | ==Basic information to include in bug reports== | ||
Revision as of 16:52, 12 September 2010
Places to report bugs
The official place to report bugs or make feature requests is the NFSv4 development list, nfsv4 at linux-nfs.org.
There is also a Bugzilla bug tracker where known bugs are tracked. You probably should review this list before reporting your issue, in case it is already known.
Basic information to include in bug reports
Please be sure to always include at least the following information when reporting an NFSv4 bug:
- The command(s) you were trying to run
- The exact error message(s) you saw, and/or symptoms encountered
- Which kernel versions are you using on the client and server?
- Are you using any of the security options?
- Results of `exportfs -v` on the server
Advanced information to include in bug reports
Depending on the nature of your bug, some of the following may also be useful to troubleshoot your problem:
- tcpdump
- system trace
- Which versions of acl, libgssapi, libevent, librpcsecgss, nfs-utils, and util-linux?
