Documentation #53054
closedceph-fuse seems to need root permissions to mount (ceph-fuse-15.2.14-1.fc33.x86_64) (documentation issue?)
0%
Description
I am running a minimal ceph cluster and am able to mount the filesystem using both kernel and ceph-fuse (as root)
However if I try a ceph-fuse mount using a normal user, the ceph-fuse mount fails.
$ ceph-fuse --id client-1 ~/mnt/mycephfs -f -d --debug-client=20 --debug-ms=1 --debug-monc=20
...
mount: /home/user/mnt/mycephfs: must be superuser to use mount.
2021-10-27T01:04:49.826+0100 7f7f9d7fa640 -1 client.314553 failed to remount (to trim kernel dentries): return code = 32
2021-10-27T01:04:49.826+0100 7f7f9d7fa640 -1 client.314553 failed to remount for kernel dentry trimming; quitting!
...
2021-10-27T01:04:49.832+0100 7f7fa5ffb640 20 client.314553 handle_client_reply got a reply. Safe:1 tid 7
2021-10-27T01:04:49.832+0100 7f7fa5ffb640 10 client.314553 insert_trace from 2021-10-27T01:04:49.833664+0100 mds.0 is_target=1 is_dentry=0Aborted (core dumped)
I've enabled user_allow_other in fuse.conf:
@[~] $ cat /etc/fuse.conf- mount_max = 1000
user_allow_other
@
I've tried disabling authentication:
auth cluster required = none
auth service required = none
auth client required = none
the main issue seems to be this error in the output of the ceph-fuse mount command:
@mount: /home/user/mnt/mycephfs: must be superuser to use mount.
2021-10-27T01:04:49.826+0100 7f7f9d7fa640 -1 client.314553 failed to remount (to trim kernel dentries): return code = 32
@
there doesn't seem to be an option to get around that, unless I am missing something
Files
Updated by Tom H over 2 years ago
client is fedora-33:
[~] $ cat /etc/os-release
NAME=Fedora
VERSION="33 (Workstation Edition)"
ID=fedora
VERSION_ID=33
VERSION_CODENAME=""
PLATFORM_ID="platform:f33"
PRETTY_NAME="Fedora 33 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:33"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=33
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=33
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
[~] $
[~] $ rpm -qi ceph-fuse
Name : ceph-fuse
Epoch : 2
Version : 15.2.14
Release : 1.fc33
Architecture: x86_64
Install Date: Mon 18 Oct 2021 15:38:34 BST
Group : Unspecified
Size : 1637649
License : (LGPLv2.1 or LGPLv3) and CC-BY-SA-3.0 and GPLv2 and Boost-1.0 and BSD and MIT
Signature : RSA/SHA256, Fri 06 Aug 2021 17:02:15 BST, Key ID 49fd77499570ff31
Source RPM : ceph-15.2.14-1.fc33.src.rpm
Build Date : Fri 06 Aug 2021 12:43:35 BST
Build Host : buildvm-x86-03.iad2.fedoraproject.org
Packager : Fedora Project
Vendor : Fedora Project
URL : http://ceph.com/
Bug URL : https://bugz.fedoraproject.org/ceph
Summary : Ceph fuse-based client
Description :
FUSE based client for Ceph distributed network file system
Updated by Patrick Donnelly over 2 years ago
- Tracker changed from Support to Documentation
- Labels (FS) task(easy) added
Userspace ceph-fuse must be root to remount itself to flush dentries. Unfortunately the documentation, yes, should be updated about that.
Updated by Nikhilkumar Shelke over 2 years ago
- Assignee set to Nikhilkumar Shelke
Updated by Venky Shankar over 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 43886
Updated by Venky Shankar over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #53331: octopus: ceph-fuse seems to need root permissions to mount (ceph-fuse-15.2.14-1.fc33.x86_64) (documentation issue?) added
Updated by Backport Bot over 2 years ago
- Copied to Backport #53332: pacific: ceph-fuse seems to need root permissions to mount (ceph-fuse-15.2.14-1.fc33.x86_64) (documentation issue?) added
Updated by Loïc Dachary over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".