Comment 2 for bug 1402834
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote Re: [Bug 1402834] Re: fuse filesystems get disconnected on container exit | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Quoting Andy Whitcroft (<email address hidden>):
> The big question is whether we tried to unmount the mount to trigger the
> exit.
Manually reproducing these steps doesn't seem to reproduce it:
sshfs -f -d -o allow_other somehost:$HOME /tmp/d
lxc-unshare -s MOUNT -- /bin/bash
mount --bind /tmp/d /mnt
umount /mnt
umount /tmp/d
exit
# sshfs is still running
> If we just killed the fuse server then the kernel behaviour seems
> valid.
The fuse server is running on the host, not in the container. We do
not kill the fuse server. It seems as though somehow sees some event
which makes it think it should exit.
> If we attempted to unmount it, that let the server go, then the
> umount failed, that sounds wrong.
We don't do anything to let the mount on the server go. Userspace
in the container does what it does on shutdown (sync;sync;umount
or whatever)