Description of problem: fusermount utility is not available to unmount fuse mount. ceph-fuse man page has the description about fusermount but utility not available. command output: [ubuntu@host01 ~]$ sudo fusermount -u /mnt/cephfs/ sudo: fusermount: command not found Version-Release number of selected component (if applicable): ceph: ceph version 12.1.2-1.el7cp (b661348f156f148d764b998b65b90451f096cb27) luminous (rc) ceph-fuse: ceph-fuse-12.1.2-1.el7cp.x86_64 How reproducible: 2/2 Steps to Reproduce: [ubuntu@host01 ~]$ sudo fusermount -u /mnt/cephfs/ sudo: fusermount: command not found Actual results: utility not available to unmount fuse mount Expected results: NA Additional info: NA
/usr/bin/fusermount is in the "fuse" RPM package. Looks like ceph-fuse depends on "fuse-libs", not "fuse". I wonder if the docs should be updated to tell users to mount with "mount" rather than "fusermount"? That's what mounting via /etc/fstab does, right?
Docs in question: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/ceph_file_system_guide_technology_preview/mounting_and_unmounting_ceph_file_systems#unmounting_ceph_file_systems simple `umount` gets a EPERM on my system while `fusermount -u` works. I believe we will need to add the fuse dependency.
Rachana can you please verify "yum install fuse" allows you to proceed?
"yum install fuse" works but it picks package from RHEL repo, after installation "fusermount" utility available.
Ken, how should we proceed on fixing the package dependencies?
I've reviewed the Debian packaging and this has been implemented since the very beginning. We just missed the "Requires: fuse" on the RPM side. https://github.com/ceph/ceph/pull/17120 adds it.
Moving this bug to verified state. fusermount mount utility available part of ceph-fuse package. Verified in build: 12.2.0-1.el7cp (b661348f156f148d764b998b65b90451f096cb27) luminous (rc)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3387