Project

General

Profile

Actions
Copy link

Documentation #6547

closed

should document magic data/journal partition types

Added by Dan Mick over 10 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

We should write down the requirements for the Ceph startup scripts to automatically mount and start OSDs:
1) gpt labels, 2) required partition UUIDs to mark partitions as OSD data/journal (or dmcrypted data/journal)

ceph-deploy creates these partitions, but only if you give it a whole disk; otherwise people are confused
why their OSDs don't start automatically. If we document it it'll explain.

Actions
Copy link
 #1

Updated by Dan Mick over 10 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #2

Updated by Dan Mick over 10 years ago

OSD data: 4fbd7e29-9d25-41b8-afd0-062c0ceff05d
OSD journal: 45b0969e-9b03-4f30-b4c6-b4b80ceff106

Actions
Copy link
 #3

Updated by John Spray about 10 years ago

hmm, is this meant to be in the calamari product?

Actions
Copy link
 #4

Updated by Dan Mick about 10 years ago

  • Project changed from 16 to Ceph
Actions
Copy link
 #5

Updated by Dan Mick about 10 years ago

No, thanks, fixed

Actions
Copy link
 #6

Updated by Zac Dover over 4 years ago

  • Status changed from New to Closed

This bug has been judged too old to fix. This is because either it is either 1) raised against a version of Ceph prior to Luminous, or 2) just really old, and untouched for so long that it is unlikely nowadays to represent a live documentation concern.

If you think that the closing of this bug is an error, raise another bug of a similar kind. If you think that the matter requires urgent attention, please let Zac Dover know at .

Actions
Copy link

Also available in: Atom PDF