Mirror
/
mergerfs
mirror of https://github.com/trapexit/mergerfs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
1506 Commits
52 Branches
97 Tags
50 MiB
 
 
 
 
Tree: 3394e7ec8b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '3394e7ec8b'
${ noResults }
mergerfs/.github/ISSUE_TEMPLATE/bug_report.md

2.4 KiB
Raw Blame History

name about title labels assignees
Bug report For the reporting of behavior not as described bug, investigating

See also https://trapexit.github.io/mergerfs/latest/support

Describe the bug

A clear and concise description of the unexpected behavior.

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. Support will NOT be provided for old versions.

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.

To Reproduce

Provide steps to reproduce the behavior. List all steps to reproduce. All settings. The version of all software involved.

Please simplify the reproduction as much as possible.

  • Unless it is dependenat on multiple branches, use a single branch
  • Reproduce with standard tooling if possible (touch,truncate,rm,rmdir,ln,etc.) Having to install 3rd party software will make debugging more difficult.

Expected behavior

A clear and concise description of the expected behavior.

Workarounds already tested

Please list all workarounds attempted and why they were ruled out as options.

System information:

  • Attach output from mergerfs.collect-info tool.
  • Alternatively:
    • OS: lsb_release -a
    • kernel version: uname -a
    • mergerfs version: mergerfs --version
    • mergerfs settings / arguments: from fstab, systemd unit, command line, OMV plugin, etc.
    • List of drives, filesystems, & sizes:
      • df -h
      • lsblk -o NAME,FSTYPE,FSSIZE,SIZE,MOUNTPOINTS,RM,RO,ROTA
    • All information about the relevant paths and files: permissions, ownership, etc.
    • All information about the application making the requests: version, uid/gid
  • Is mergerfs running within a container or used with container technologies?
  • Are the client apps using mergerfs running in a container?
  • A strace of the application having a problem:
    • strace -fvTtt -s 256 -o /tmp/app.strace.txt <cmd>
    • strace -fvTtt -s 256 -o /tmp/app.strace.txt -p <appPID>
  • strace of mergerfs while app tried to do it's thing:
    • strace -fvTtt -s 256 -p <mergerfsPID> -o /tmp/mergerfs.strace.txt

Additional context

Add any other context about the problem here.