mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-10-26 19:01:56 -04:00
77 lines
2.4 KiB
Markdown
77 lines
2.4 KiB
Markdown
---
|
|
name: Bug report
|
|
about: For the reporting of behavior not as described
|
|
title: ''
|
|
labels: bug, investigating
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
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](https://trapexit.github.io/mergerfs/latest/tooling/#mergerfscollect-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.
|