udev vs fuse: Transport endpoint is not connected

[Mathieu Malaterre]

Could a udev guru please comment on the (somewhat) famous issue
`Transport endpoint is not connected` happening when a udev rule tries
to mount fuse filesystem ? The only description I found of this issue
appear on archlinux wiki, it does not explain the actual issue: it
only tells you one should not do it. Why is this so fundamentally
wrong ? Can this be fixed ?

Bug #774149 has surfaced since jessie now default to using ntfs-3g
when mounting ntfs filesystem.

Thx for comment,

[Dominique Dumont]

Post by Mathieu Malaterre
Could a udev guru please comment on the (somewhat) famous issue
`Transport endpoint is not connected` happening when a udev rule tries
to mount fuse filesystem ? The only description I found of this issue
appear on archlinux wiki, it does not explain the actual issue: it
only tells you one should not do it. Why is this so fundamentally
wrong ? Can this be fixed ?

I often had this error while debugging Config::Model::FuseUI

You should be able to fix this issue by running
'fusermount -u broken-mount-point'

For more details, see this stackoverflow answer [2]

HTH

[1] http://search.cpan.org/perldoc?Config%3A%3AModel%3A%3AFuseUI
[2] http://stackoverflow.com/questions/16002539/fuse-error-transport-endpoint-is-not-connected

[Mathieu Malaterre]

Post by Dominique Dumont

Post by Mathieu Malaterre
Could a udev guru please comment on the (somewhat) famous issue
`Transport endpoint is not connected` happening when a udev rule tries
to mount fuse filesystem ? The only description I found of this issue
appear on archlinux wiki, it does not explain the actual issue: it
only tells you one should not do it. Why is this so fundamentally
wrong ? Can this be fixed ?

I often had this error while debugging Config::Model::FuseUI
You should be able to fix this issue by running
'fusermount -u broken-mount-point'

I've seen this suggested before, thanks.

However my questions were:
1. What is the actual issue of ``udev`` vs ``fuse``
2. What (if possible) is needed to make a *udev* rules mount a FUSE
filesystem (I do not really care for proper umount for now).

I can mount/umount just fine from the command line. There is something
very low level happening when (fuse)mounting within a udev rules.

Thanks again.

[Alastair McKinstry]

I have seen this issue outside of udev, for iRODS mounting filesystems
via fuse;
if there was a break in connectivity (network) the kernel driver would
crash,
and this problem would occur.

Post by Mathieu Malaterre

Post by Dominique Dumont

Post by Mathieu Malaterre
Could a udev guru please comment on the (somewhat) famous issue
`Transport endpoint is not connected` happening when a udev rule tries
to mount fuse filesystem ? The only description I found of this issue
appear on archlinux wiki, it does not explain the actual issue: it
only tells you one should not do it. Why is this so fundamentally
wrong ? Can this be fixed ?

I often had this error while debugging Config::Model::FuseUI
You should be able to fix this issue by running
'fusermount -u broken-mount-point'

I've seen this suggested before, thanks.
1. What is the actual issue of ``udev`` vs ``fuse``
2. What (if possible) is needed to make a *udev* rules mount a FUSE
filesystem (I do not really care for proper umount for now).
I can mount/umount just fine from the command line. There is something
very low level happening when (fuse)mounting within a udev rules.
Thanks again.

[Dominique Dumont]

Post by Mathieu Malaterre
1. What is the actual issue of ``udev`` vs ``fuse``
2. What (if possible) is needed to make a *udev* rules mount a FUSE
filesystem (I do not really care for proper umount for now).

I can only guess that:
- mounting a file system with fuse is based on file /dev/fuse
- /dev/fuse is set up by udev
- there's a race condition between the setup of /dev/fuse and ntfs-3g mounts.

Note that I could be completely wrong. But I would search in that area

Hope this helps

[Marco d'Itri]

Post by Mathieu Malaterre
Could a udev guru please comment on the (somewhat) famous issue
`Transport endpoint is not connected` happening when a udev rule tries
to mount fuse filesystem ? The only description I found of this issue

I think that the fuse process is being killed.
You cannot start long-lived processes from a udev rule, this should be
handled by systemd.