Journal header should be repaired when ceph is started, unless something changed with Mimic, the message you see should be treated as a warning ( 2019-05-30 17:58:23.946 7efc5f5751c0 -1 journal FileJournal::open: ondisk fsid 00000000-0000-0000-0000-000000000000 doesn't match expected f89591cf-a74f-4cff-85ed-8f93103267e0, invalid (someone else's?) journal ).
The journal partition is empty, cheps-osd sees this and initializes it as journal =» OSD should start correctly. Question is, why does it sometimes fail? It starts correctly most of the time...
So, if DB/manifest entries are ok, and the proposed fix works when moving journal from collocated to external on an existing OSD, please check one more more thing: when adding a new OSD with external journal (do not unlock, add a new OSD, collocate it to /dev/sdc1, then unlock) will you still see /dev/sdb1 and /dev/sdb2? It has to be there as user should be able to fallback to collocated in case the journal drive breaks (this was a product requirement at the time of implementation).
Hi Chen,
Journal header should be repaired when ceph is started, unless something changed with Mimic, the message you see should be treated as a warning ( 2019-05-30 17:58:23.946 7efc5f5751c0 -1 journal FileJournal::open: ondisk fsid 00000000- 0000-0000- 0000-0000000000 00 doesn't match expected f89591cf- a74f-4cff- 85ed-8f93103267 e0, invalid (someone else's?) journal ).
The journal partition is empty, cheps-osd sees this and initializes it as journal =» OSD should start correctly. Question is, why does it sometimes fail? It starts correctly most of the time...
So, if DB/manifest entries are ok, and the proposed fix works when moving journal from collocated to external on an existing OSD, please check one more more thing: when adding a new OSD with external journal (do not unlock, add a new OSD, collocate it to /dev/sdc1, then unlock) will you still see /dev/sdb1 and /dev/sdb2? It has to be there as user should be able to fallback to collocated in case the journal drive breaks (this was a product requirement at the time of implementation).