Bug 1817179

Summary: [abrt] ceph-fuse: ceph::__ceph_abort(): ceph-fuse killed by SIGABRT
Product: [Fedora] Fedora Reporter: Patrick C. F. Ernzer <pcfe>
Component: cephAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: branto, danmick, david, fedora, i, josef, kkeithle, loic, ramkrsna, steve, zyan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/811975de8ca22f1262ed810917c11dccf544deb1
Whiteboard: abrt_hash:b18a82378aeaf06fc8a45c5a575e19e23a364074;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 20:20:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Patrick C. F. Ernzer 2020-03-25 18:08:46 UTC
Description of problem:
Tried to mount as follows

[root@t7910 ~]# ceph-fuse -n client.workstation_pcfe /mnt/cephfs
2020-03-25 17:08:39.865 7f782976ff00 -1 init, newargv = 0x555dcb9a99f0 newargc=7
ceph-fuse[5057]: starting ceph client
ceph-fuse[5057]: starting fuse
[root@t7910 ~]# mount: /mnt/cephfs: mount point not mounted or bad option.

/etc/ceph/ contains ceph.confg and ceph.client.workstation_pcfe.keyring

Version-Release number of selected component:
2:ceph-fuse-14.2.8-1.fc31

Additional info:
reporter:       libreport-2.12.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-3.scope
cmdline:        ceph-fuse -n client.workstation_pcfe /mnt/cephfs
crash_function: ceph::__ceph_abort
executable:     /usr/bin/ceph-fuse
journald_cursor: s=32e62b6facb0491d9cc7776ed55f2eb2;i=cf556;b=f95992ee819e4252b4a384168b8b74c8;m=d5831c5;t=5a1b014e910dd;x=f6c39a475985e4c7
kernel:         5.5.10-200.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 1 Patrick C. F. Ernzer 2020-03-25 18:08:52 UTC
Created attachment 1673584 [details]
File: backtrace

Comment 2 Patrick C. F. Ernzer 2020-03-25 18:08:55 UTC
Created attachment 1673585 [details]
File: core_backtrace

Comment 3 Patrick C. F. Ernzer 2020-03-25 18:08:56 UTC
Created attachment 1673586 [details]
File: cpuinfo

Comment 4 Patrick C. F. Ernzer 2020-03-25 18:08:59 UTC
Created attachment 1673587 [details]
File: dso_list

Comment 5 Patrick C. F. Ernzer 2020-03-25 18:09:01 UTC
Created attachment 1673588 [details]
File: environ

Comment 6 Patrick C. F. Ernzer 2020-03-25 18:09:02 UTC
Created attachment 1673589 [details]
File: limits

Comment 7 Patrick C. F. Ernzer 2020-03-25 18:09:04 UTC
Created attachment 1673590 [details]
File: maps

Comment 8 Patrick C. F. Ernzer 2020-03-25 18:09:06 UTC
Created attachment 1673591 [details]
File: mountinfo

Comment 9 Patrick C. F. Ernzer 2020-03-25 18:09:08 UTC
Created attachment 1673592 [details]
File: open_fds

Comment 10 Patrick C. F. Ernzer 2020-03-25 18:09:09 UTC
Created attachment 1673593 [details]
File: proc_pid_status

Comment 11 Yan, Zheng 2020-03-31 02:48:21 UTC
does /etc/fstab contain an entry for kernel cephfs mount on /mnt/cephfs?

does dmesg output contain error "fuse: Unknown parameter 'name'" ?

Comment 12 Patrick C. F. Ernzer 2020-04-02 09:26:38 UTC
(In reply to Yan, Zheng from comment #11)
> does /etc/fstab contain an entry for kernel cephfs mount on /mnt/cephfs?

nope, only fuse;
[root@t7910 tmp]# grep ceph /etc/fstab 
# c.f. /usr/sbin/mount.fuse.ceph
# note that wioth ceph.id I get errors, so try ceph.name instead
none       /mnt/cephfs  fuse.ceph   ceph.name=client.workstation_pcfe,_netdev,noauto  0 0
#none       /mnt/cephfs  fuse.ceph   ceph.id=workstation_pcfe,_netdev,noauto  0 0
#none    /mnt/ceph  fuse.ceph   ceph.name=client.admin,_netdev,defaults  0 0

> does dmesg output contain error "fuse: Unknown parameter 'name'" ?

tried both. But yes from some tries I do get a
Mar 25 17:08:39 t7910.internal.pcfe.net kernel: fuse: Unknown parameter 'ceph.name'
entry in my logs.


If need be I can delete all related entries in the F31 box' fstab, reboot and retry.

Are you able to reproduce this on a F31 x86_64 client accessing a RHCS Nautilus cluster?
(reason I ask is that I am still not sure if I did not simply fat finger something on my client machine)

Comment 13 Yan, Zheng 2020-04-03 02:22:23 UTC
https://github.com/ceph/ceph/pull/34306

Comment 14 Kaleb KEITHLEY 2020-05-21 14:19:52 UTC
fixed in ceph-15.2.2
fix landing in ceph-14.2.10
wlll keep this open until 14.2.10 is released

Comment 15 Patrick C. F. Ernzer 2020-09-17 09:54:13 UTC
14.2.11 is in currently released Fedora (32), I think we can close this.

Comment 16 Ben Cotton 2020-11-03 16:31:37 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Ben Cotton 2020-11-24 20:20:18 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.