Comment 2 for bug 1934775

I guess this can be fixed by manually bind mounting /target/sys/fs/fuse/connections as we currently do for /target/sys/firmware/efi/efivars. But I don't understand why either of these is needed, unless /sys/fs/fuse/connections is not mounted before the install starts, because this sequence works for me:

root@venerated-bobcat:~/t# mkdir a a/b c
root@venerated-bobcat:~/t# mount -t fusectl fusectl a/b
root@venerated-bobcat:~/t# mount --bind a c
root@venerated-bobcat:~/t# umount c

This sequence does not:

root@venerated-bobcat:~/t# mkdir a a/b c
root@venerated-bobcat:~/t# mount --bind a c
root@venerated-bobcat:~/t# mount -t fusectl fusectl a/b
root@venerated-bobcat:~/t# umount c
umount: /root/t/c: target is busy.

But afaics /sys/fs/fuse/connections is mounted at startup (it's "wanted" by sysinit.target). So I don't know what's going on basically. But I can probably fix it anyway if it's urgent.