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.

45 lines
2.2 KiB

  1. # Support
  2. Filesystems are complex, as are the interactions software have with
  3. them, and therefore difficult to debug. When reporting on a suspected
  4. issue **please** include as much of the below information as possible
  5. otherwise it will be difficult or impossible to diagnose. Also please
  6. read the documentation as it provides details on many previously
  7. encountered questions/issues.
  8. **Please make sure you are using the [latest
  9. release](https://github.com/trapexit/mergerfs/releases) or have tried
  10. it in comparison. Old versions, which are often included in distros
  11. like Debian and Ubuntu, are not ever going to be updated and the issue
  12. you are encountering may have been addressed already.**
  13. **For commercial support or feature requests please [contact me
  14. directly.](mailto:support@spawn.link)**
  15. ### Information to include in bug reports
  16. * [Information about the broader problem along with any attempted
  17. solutions.](https://xyproblem.info)
  18. * Solution already ruled out and why.
  19. * Version of mergerfs: `mergerfs --version`
  20. * mergerfs settings / arguments: from fstab, systemd unit, command
  21. line, OMV plugin, etc.
  22. * Version of the OS: `uname -a` and `lsb_release -a`
  23. * List of branches, their filesystem types, sizes (before and after issue): `df -h`
  24. * **All** information about the relevant paths and files: permissions, ownership, etc.
  25. * **All** information about the client app making the requests: version, uid/gid
  26. * Runtime environment:
  27. * Is mergerfs running within a container?
  28. * Are the client apps using mergerfs running in a container?
  29. * A `strace` of the app having problems:
  30. * `strace -fvTtt -s 256 -o /tmp/app.strace.txt <cmd>`
  31. * A `strace` of mergerfs while the program is trying to do whatever it is failing to do:
  32. * `strace -fvTtt -s 256 -p <mergerfsPID> -o /tmp/mergerfs.strace.txt`
  33. * **Precise** directions on replicating the issue. Do not leave **anything** out.
  34. * Try to recreate the problem in the simplest way using standard programs: `ln`, `mv`, `cp`, `ls`, `dd`, etc.
  35. ### Contact / Issue submission
  36. * github.com: [https://github.com/trapexit/mergerfs/issues](https://github.com/trapexit/mergerfs/issues)
  37. * discord: [https://discord.gg/MpAr69V](https://discord.gg/MpAr69V)
  38. * reddit: [https://www.reddit.com/r/mergerfs](https://www.reddit.com/r/mergerfs)