ghbiz
76 Posts
Quote from ghbiz on February 16, 2019, 10:15 pm
Looks like we were able to reproduce this accordingly.
Step1. Cause a OSD to fail by pulling disk out.
Step2. in PetSAN gui, click on Delete Icon on Failed OSD.
OSD will delete but journal partition belonging to the OSD remains.
Looks like we were able to reproduce this accordingly.
Step1. Cause a OSD to fail by pulling disk out.
Step2. in PetSAN gui, click on Delete Icon on Failed OSD.
OSD will delete but journal partition belonging to the OSD remains.
ghbiz
76 Posts
Quote from ghbiz on May 24, 2019, 2:30 am
do we know if this was fixed in 2.3?
do we know if this was fixed in 2.3?
admin
2,918 Posts
Quote from admin on May 24, 2019, 1:49 pm
it is still there. Currently we do not remove journal partitions but create a new one for each new osd. We were discussing adding this recently, the trick here is that although we can easily know the journal partition looking at the osd but it is not as easy to know the osd by just looking at the journal partition. We also do not want to re-use a journal partition if its original osd will be back sometime.
it is still there. Currently we do not remove journal partitions but create a new one for each new osd. We were discussing adding this recently, the trick here is that although we can easily know the journal partition looking at the osd but it is not as easy to know the osd by just looking at the journal partition. We also do not want to re-use a journal partition if its original osd will be back sometime.
