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.

49 lines
1.5 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 the unexpected behavior.
  10. **Please be sure to use latest release of mergerfs to ensure the issue still exists. Not your distro's latest but the latest official release.**
  11. The master branch is **not** to be considered production ready. Feel free to file bug reports but do so indicating clearly that you are testing unreleased code.
  12. **To Reproduce**
  13. Steps to reproduce the behavior. List **all** steps to reproduce. **All** settings.
  14. Please simplify the reproduction as much as possible.
  15. - Unless it is dependenat on multiple branches, use a single branch
  16. - Reproduce with standard tooling if possible (touch,truncate,rm,rmdir,ln,etc.) Having to install 3rd party software will make debugging more difficult.
  17. **Expected behavior**
  18. A clear and concise description of the expected behavior.
  19. **System information:**
  20. - OS, kernel version: `uname -a`
  21. - mergerfs version: `mergerfs -V`
  22. - mergerfs settings
  23. - List of drives, filesystems, & sizes:
  24. - `df -h`
  25. - `lsblk -f`
  26. - A strace of the application having a problem:
  27. - `strace -fvTtt -s 256 -o /tmp/app.strace.txt <cmd>`
  28. - `strace -fvTtt -s 256 -o /tmp/app.strace.txt -p <appPID>`
  29. - strace of mergerfs while app tried to do it's thing:
  30. - `strace -fvTtt -s 256 -p <mergerfsPID> -o /tmp/mergerfs.strace.txt`
  31. **Additional context**
  32. Add any other context about the problem here.