|
Ok sorry for spamming. I got it fixed and I figured I better share what I did wrong. I reused my logical volume and using the same size as before and then it just kept the old journal (this is what I guess I guess). I changed the size of my logical volume and now it is working. (I change to using private email, this is not really something work related= Cheers, Claes From: Sahlstrom, Claes
I should probably add that I have tried to use
–mkjournal In my case “ceph-osd -i 5 --mkjournal” and I thought that would be the magic I needed. From: Sahlstrom, Claes
Hi, I have a problem starting a couple of OSDs because of the journal being corrupt. Is there any way to replace the journal and keeping the rest of the OSD intact. -1> 2015-01-11 16:02:54.475138 7fb32df86900 -1 journal Unable to read past sequence 8188178 but header indicates the journal has committed up through 8188206, journal is corrupt 0> 2015-01-11 16:02:54.479296 7fb32df86900 -1 os/FileJournal.cc: In function 'bool FileJournal::read_entry(ceph::bufferlist&, uint64_t&, bool*)' thread 7fb32df86900 time 2015-01-11 16:02:54.475276 os/FileJournal.cc: 1693: FAILED assert(0) I ended up in this situation when osd.9 on host “orange” went down, and then I had a powerfailure on the host “purple” which made 2 of my journals corrupt. -3 6 host purple 4 1 osd.4 up 1 5 1 osd.5 down 0 7 2 osd.7 down 0 6 2 osd.6 up 1 -4 6 host orange 8 1 osd.8 up 1 9 1 osd.9 down 0 The filesystem was not in use by users, but it was replicating when the host went down and I figure that I still have the data on the OSD-disks, they are still mountable and the XFS-filesystem on them seems to be intact. Thanks, Claes |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
