You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# mount.lklfuse is a simple wrapper around the binary called below# <parse arguments to extract type string and escape remaining mount options>
/usr/bin/lklfuse "$dev""$mnt" -o "type=${typeopt},opts=${optsopt}"
This appears to work okay in that lklfuse starts and successfully mounts the block device. However, udisksd immediately fails the subsequent!is_mounted check, due to the lack of block device node presence in /proc/self/mountinfo. The mountinfo entry for the successful lklfuse mount instead corresponds to a FUSE-derived MAJOR:MINOR.
I'm just wondering how to best resolve this issue. The simplest might be to simply check wether the mountpoint is present in mountinfo, instead of the MAJOR:MINOR, or perhaps ignore the is_mounted check if a specific config flag is present.
I'd appreciate any other tips or suggestions.
The text was updated successfully, but these errors were encountered:
I don't think there's a way to make this work from the outside. UDisks is currently heavily based on major:minor number as primary device identifier. There's a dirty workaround for btrfs, nothing for fuse AFAIK. Interesting that ntfs-3g mounts do work fine.
Hi,
I'm trying to use
udisks2
alongside lklfuse, which gets invoked via the followingmount_options.conf
:This appears to work okay in that
lklfuse
starts and successfully mounts the block device. However,udisksd
immediately fails the subsequent!is_mounted
check, due to the lack of block device node presence in/proc/self/mountinfo
. Themountinfo
entry for the successfullklfuse
mount instead corresponds to a FUSE-derivedMAJOR:MINOR
.I'm just wondering how to best resolve this issue. The simplest might be to simply check wether the mountpoint is present in
mountinfo
, instead of theMAJOR:MINOR
, or perhaps ignore theis_mounted
check if a specific config flag is present.I'd appreciate any other tips or suggestions.
The text was updated successfully, but these errors were encountered: