Hi Dmitry,
I think you are confusing mounting into a directory that already contains files
with re-mounting the same filesystem on top of itself.
Refusing to use a non-empty directory as a mountpoint does not prevent you from
mounting the same filesystem multiple times, because the file system
> ...the one who mounts the filesystem need to be sure
> s/he doesn't shadow real files / directories with the mount.
No, this is a very unsafe default because benign `mount -av` will create more
layered mounts on every invocation.
Mount should be idempotent by default.
> This is the same
Hi,
Some files systems (eg S3QL) pass this option automatically to libfuse, in an
attempt behave like regular mount even for libfuse 2.x. The user has no control
over this, so the filesystem becomes unusable.
Best,
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
On Sun, Sep 8, 2019 at 5:24 PM Nikolaus Rath wrote:
> fuse3 currently declares 'Replaces: fuse', but it is not actually a
> drop-in replacement. FUSE 2.x filesystems that use the '-o nonempty' mount
> option (which was removed in FUSE 3) break with
>
> fusermount: unknown option 'nonempty'
>
> if
Package: fuse3
Version: 3.4.1-1
Severity: important
fuse3 currently declares 'Replaces: fuse', but it is not actually a
drop-in replacement. FUSE 2.x filesystems that use the '-o nonempty' mount
option (which was removed in FUSE 3) break with
fusermount: unknown option 'nonempty'
if fuse3 is
5 matches
Mail list logo
