You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

34 lines
1.2 KiB

  1. ---
  2. name: Bug report
  3. about: For the reporting of behavior not as described
  4. title: ''
  5. labels: bug, investigating
  6. assignees: ''
  7. ---
  8. **Describe the bug**
  9. A clear and concise description of what the bug is. Please do not file bugs for unreleased versions unless you're a tester or sure it's not a work in progress. The master branch is **not** to be considered in a production state.
  10. **To Reproduce**
  11. Steps to reproduce the behavior. List **all** steps to reproduce. **All** settings.
  12. Please simplify the reproduction as much as possible.
  13. - Unless it is dependenat on multiple branches, use a single branch
  14. - Use basic tooling if possible (touch,truncate,rm,rmdir,ln,etc.)
  15. **Expected behavior**
  16. A clear and concise description of what you expected to happen.
  17. **System information:**
  18. - OS, kernel version: `uname -a`
  19. - mergerfs version: `mergerfs -V`
  20. - mergerfs settings
  21. - List of drives, filesystems, & sizes: `df -h`
  22. - A strace of the application having a problem: `strace -f -o /tmp/app.strace.txt <cmd>` or `strace -f -p <appPID> -o /tmp/app.strace.txt`
  23. - strace of mergerfs while app tried to do it's thing: `strace -f -p <mergerfsPID> -o /tmp/mergerfs.strace.txt`
  24. **Additional context**
  25. Add any other context about the problem here.