2020-08-01 12:07:50 +08:00
---
name: Bug report
about: For the reporting of behavior not as described
title: ''
labels: bug, investigating
assignees: ''
---
**Describe the bug**
2021-03-15 19:58:02 +08:00
2021-08-10 09:09:54 +08:00
A clear and concise description of the unexpected behavior. Please be sure to use latest release of mergerfs to ensure the issue still exists.
2021-03-15 19:58:02 +08:00
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.
2020-08-01 12:07:50 +08:00
**To Reproduce**
2021-03-15 19:58:02 +08:00
2020-09-13 22:28:20 +08:00
Steps to reproduce the behavior. List **all** steps to reproduce. **All** settings.
Please simplify the reproduction as much as possible.
- Unless it is dependenat on multiple branches, use a single branch
2021-08-10 09:09:54 +08:00
- Use standard tooling if possible (touch,truncate,rm,rmdir,ln,etc.)
2020-09-13 22:28:20 +08:00
2020-08-01 12:07:50 +08:00
**Expected behavior**
2021-03-15 19:58:02 +08:00
2021-08-10 09:09:54 +08:00
A clear and concise description of the expected behavior.
2020-08-01 12:07:50 +08:00
2020-09-13 22:28:20 +08:00
2020-08-01 12:07:50 +08:00
**System information:**
2021-03-15 19:58:02 +08:00
2020-08-01 12:07:50 +08:00
- OS, kernel version: `uname -a`
- mergerfs version: `mergerfs -V`
- mergerfs settings
2021-03-15 19:58:02 +08:00
- List of drives, filesystems, & sizes:
- `df -h`
2022-01-19 10:15:59 +08:00
- `lsblk -f`
2021-03-15 19:58:02 +08:00
- 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`
2020-08-01 12:07:50 +08:00
**Additional context**
2021-03-15 19:58:02 +08:00
2020-08-01 12:07:50 +08:00
Add any other context about the problem here.
