trapexit

Is the original mergerfs instance being umounted? That's not the default behavior. In fact lazy umount of the underlying mountpoint was only added recently. I'm not entirely sure what is...

>That means no umounting, just mounting over the previous mount. I also have lazy mount enabled. It is lazy unmount. Not mount. Is `lazy-umount-mountpoint=true` ? And if so is the...

> Sure, it's no surprise if you know this stuff. For the average user it might be confusing. I've no problem adding details about external dependencies. I do it all...

Sure. I'll try to take a look this weekend. I don't use any network filesystems with mergerfs for anything serious so I'll have to set it all up from scratch.

https://github.com/containers/oci-umount/issues/48 I found random other comments around that suggest that lazy umount of exported NFS shares isn't a good idea. So I guess I'll put a note in the argument...

I didn't provide links to everything I found. It's related. lazy umount removes the mount from the filesystem tree as it mentions in that link. Clearly that leads to issues...

You have to run exportfs again because it is a new filesystem and the fact the old filesystem is half removed clearly causes issues with new clients. Depends on what...

> I can definitely live with this. There really isn't any alternative. It's not impossible but very much not practical to replace the running process. Even if I could certain...

As for the runtime API. I already support some things over ioctl and will be deprecating the xattr interface come v3. But will require changes to all existing tooling naturally.

You don't. It isn't a key value pair. It is a flag. It writes any details to /tmp/mergerfs..info What are you trying to do/learn exactly?