Did the journal drive fail during operation? Or was it taken out during pre-failure. If it fully failed, then most likely you can't guarantee the consistency of the underlying osds. In this case, you just put the affected osds and add them back in as new osds.
In the case of having good data on the osds, you follow the standard process of closing the journal, create the new partition, set up all of the partition metadata so that the ceph udev rules will know what the journal is, and just create a new dmcrypt volume on it. I would recommend using the same uuid as the old journal so that you don't need to update the symlinks and such on the osd. After everything is done, run the journal create command for the osd and start the osd. On Tue, Sep 5, 2017, 2:47 AM M Ranga Swami Reddy <[email protected]> wrote: > Hello, > How to replace an OSD's journal created with dmcrypt, from one drive > to another drive, in case of current journal drive failed. > > Thanks > Swami > _______________________________________________ > ceph-users mailing list > [email protected] > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
