Re: [ceph-users] Crashed MDS (segfault)

2019-10-25 Thread Gustavo Tonini
Well, I coundn't identify which object I need to "rmomapkey" as instructed in https://tracker.ceph.com/issues/38452#note-12. This is the log around the crash: https://pastebin.com/muw34Qdc On Fri, Oct 25, 2019 at 11:27 AM Yan, Zheng wrote: > On Fri, Oct 25, 2019 at 9:42 PM G

Re: [ceph-users] Crashed MDS (segfault)

2019-10-25 Thread Gustavo Tonini
ently due to the bug described at https://tracker.ceph.com/issues/38452 On Wed, Oct 23, 2019, 02:24 Yan, Zheng wrote: > On Tue, Oct 22, 2019 at 1:49 AM Gustavo Tonini > wrote: > > > > Is there a possibility to lose data if I use "cephfs-data-scan init > --force-init&q

Re: [ceph-users] Crashed MDS (segfault)

2019-10-21 Thread Gustavo Tonini
Is there a possibility to lose data if I use "cephfs-data-scan init --force-init"? On Mon, Oct 21, 2019 at 4:36 AM Yan, Zheng wrote: > On Fri, Oct 18, 2019 at 9:10 AM Gustavo Tonini > wrote: > > > > Hi Zheng, > > the cluster is running ceph mimic. This warning

Re: [ceph-users] Crashed MDS (segfault)

2019-10-17 Thread Gustavo Tonini
ds/SnapRealm.cc#L599 ? Is there a way to fix this? On Thu, Oct 17, 2019 at 9:58 PM Yan, Zheng wrote: > On Thu, Oct 17, 2019 at 10:19 PM Gustavo Tonini > wrote: > > > > No. The cluster was just rebalancing. > > > > The journal seems damaged: > > > > ceph@depl

[ceph-users] Crashed MDS (segfault)

2019-10-14 Thread Gustavo Tonini
Dear ceph users, we're experiencing a segfault during MDS startup (replay process) which is making our FS inaccessible. MDS log messages: Oct 15 03:41:39.894584 mds1 ceph-mds: -472> 2019-10-15 00:40:30.201 7f3c08f49700 1 -- 192.168.8.195:6800/3181891717 <== osd.26 192.168.8.209:6821/2419345 3