Hi Willem,

The only reference to "nonempty" in binds code is when a directory is
mounted on itself. In that case bindfs adds `-ononempty` automatically. I
changed it so it doesn't on FUSE 3:
https://github.com/mpartel/bindfs/commit/2c2337b7c9b87744662c4b08d453bf7128444f43
(git master, not in a release yet)

If that doesn't help, maybe you're running a mixed environment where e.g.
bindfs is compiled against FUSE 2 but the system runs FUSE 3 helper
binaries? The version list at the end of your e-mail suggests this.
I added an option that may help you debug that:
https://github.com/mpartel/bindfs/commit/4b87500fef925e591b08cb8aea6bf0a21b84dd72

Let me know if I can help further.


On Wed, 12 Feb 2020 at 16:27, Willem Mulder <will...@scintilla.utwente.nl>
wrote:

> Package: bindfs
> Version: 1.14.1-1
> Severity: normal
> File: /usr/bin/bindfs
>
> Dear Maintainer,
>
> Currently, it's not possible for me to mount over nonempty directories.
> BindFS insists I have to use -o nonempty:
>
>     fuse: mountpoint is not empty
>     fuse: if you are sure this is safe, use the 'nonempty' mount option
>
> But when I do, I get the following message:
>
>     fusermount: unknown option 'nonempty'
>
> Some quick searching suggests this might have to do with upgrading to
> FUSE 3: https://github.com/rclone/rclone/issues/3562
>
> Kind regards,
>
> Willem Mulder
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'),
> (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.4.0-3-amd64 (SMP w/16 CPU cores)
> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages bindfs depends on:
> ii  fuse3 [fuse]  3.7.0-1
> ii  libc6         2.29-10
> ii  libfuse2      2.9.9-2
>
> bindfs recommends no packages.
>
> bindfs suggests no packages.
>
> -- no debconf information
>
>

Reply via email to