Actions
Bug #44771
closedceph-fuse: ceph::__ceph_abort(): ceph-fuse killed by SIGABRT in Client::_do_remount
% Done:
0%
Source:
Community (user)
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
ceph-fuse
Labels (FS):
crash
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Description of problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1817179
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-fuse5057: starting ceph client
ceph-fuse5057: 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
Updated by Greg Farnum about 4 years ago
- Subject changed from ceph-fuse: ceph::__ceph_abort(): ceph-fuse killed by SIGABRT to ceph-fuse: ceph::__ceph_abort(): ceph-fuse killed by SIGABRT in Client::_do_remount
- Priority changed from Normal to High
- Component(FS) ceph-fuse added
- Labels (FS) crash added
Updated by Zheng Yan about 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 34306
Updated by Greg Farnum about 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to octopus
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #45046: octopus: ceph-fuse: ceph::__ceph_abort(): ceph-fuse killed by SIGABRT in Client::_do_remount added
Updated by Nathan Cutler about 4 years ago
- Backport changed from octopus to octopus, nautilus
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #45287: nautilus: ceph-fuse: ceph::__ceph_abort(): ceph-fuse killed by SIGABRT in Client::_do_remount added
Updated by Patrick Donnelly about 4 years ago
- Target version changed from v14.2.9 to v16.0.0
- Backport changed from octopus, nautilus to octopus,nautilus
Updated by Nathan Cutler almost 4 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".
Actions