Hi Dan, At least looking at upstream to get journals and partitions persistently working, this requires gpt partitions, and being able to add a GPT partition UUID to work perfectly with minimal modification. I am not sure the status of this on RHEL6, The latest Fedora and OpenSUSE support this but SLE12 (To be released) and I think RHEL7 do support this. Im sure you can bypass this as every data partition contains a symlink to the journal partition, but persistent naming may be more work if you dont use GPT partitions. Best of luck. Owen On 09/29/2014 10:24 AM, Dan Van Der Ster wrote: > Hi, > >> On 29 Sep 2014, at 10:01, Daniel Swarbrick <daniel.swarbrick at profitbricks.com> wrote: >> >> On 26/09/14 17:16, Dan Van Der Ster wrote: >>> Hi, >>> Apologies for this trivial question, but what is the correct procedure to replace a failed OSD that uses a shared journal device? >>> >>> I?m just curious, for such a routine operation, what are most admins doing in this case? >>> >> >> I think ceph-osd is what you need. >> >> ceph-osd -i <osd id> ?mkjournal > > > At the moment I am indeed using this command to in our puppet manifests for creating and replacing OSDs. But now I?m trying to use the ceph-disk udev magic, since it seems to be the best (perhaps only?) way to get persistently named OSD and journal devs (on RHEL6). > > Cheers, Dan > _______________________________________________ > ceph-users mailing list > ceph-users at lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
 |