Race condition between mount exit and filesystem actually being mounted

slonopotamus commented 1 year ago

Way to reproduce:

mkdir aa
mkdir bb
bindfs aa bb && umount bb

There's a very high chance that you'll get umount: bb: not currently mounted

Another way to reproduce, more realistic (this is what I actually hit - trying to access files right after mounting them):

mkdir aa
touch aa/file
mkdir bb
bindfs aa bb && ls bb/file

There's a very high chance that you'll get ls: bb/file: No such file or directory

Is there any way to guarantee that by the time bindfs returns non-zero exit code filesystem is actually mounted?

My environment:

Adding sleep 1 after bindfs exit workarounds the issue, but doesn't look like a proper fix.

I haven't tried with other FUSE filesystems, but highly suspect that they will exhibit the same behaviour.

This issue does NOT reproduce if macFUSE 4.5.0 is used instead of fuse-t 1.0.23.

alexfs commented 1 year ago

Thanks for the report, I will check

slonopotamus commented 12 months ago

Confirming this is fixed in 1.0.24. Thanks!

macos-fuse-t / fuse-t