trapexit

simply run `strace -f -e write mv bb.txt aa.txt` and you will see the writing to stderr if there are errors. You can look at the trace you sent me...

I need traces where you reproduce that situation.

What's the trace when you do that?

A full trace. Remove the `-e write`

The trace will likely show you where that error comes from. Unless the error is generated by mv itself rather than a syscall.

No. Remove `-e write`. `strace -f mv bb.txt aa.txt`

That's on the volume you said was having an issue? This is succeeding. No errors.

@dpantel Please provide more information as described in the docs. OS? Version of everything involved? Etc.

https://github.com/trapexit/mergerfs#nfsopenhack >if set to git it will only perform the hack when the path in question includes `/.git/`. all will result it it applying anytime a readonly file which is...

xattr -p user.mergerfs.nfsopenhack /media/.mergerfs Of course there are other ways but you have to consider the costs of performing the checks. What would you suggest? https://github.com/trapexit/mergerfs/blob/master/src/fuse_open.cpp#L77 That's the code. As...