On Wed, Jul 11, 2018 at 3:33 PM, Huseyin Cotuk wrote:
> Dear Paul and Alfredo,
>
> Downgrading to ceph-deploy 1.5.38 did not work either. I labeled the journal
> partition (i.e. /dev/nvme0n1p12) with parted, and it added a gpt partuuid to
> this specific partition:
>
> /dev/nvme0n1p12: PTUUID="8a7
Dear Paul and Alfredo,
Downgrading to ceph-deploy 1.5.38 did not work either. I labeled the journal
partition (i.e. /dev/nvme0n1p12) with parted, and it added a gpt partuuid to
this specific partition:
/dev/nvme0n1p12: PTUUID="8a775205-1364-43d9-820e-c4d3a0d9f9e3" PTTYPE="gpt"
PARTLABEL="ceph
On Wed, Jul 11, 2018 at 12:57 PM, Huseyin Cotuk wrote:
> Hi Paul,
>
> Thanks for your reply. I did not mention any special parameter while
> upgrading to luminous. So this ceph-deploy version is the one coming from
> the official debian luminous repo.
That is because ceph-volume came out in Lumin
Luminous repo comes with ceph-deploy 2.0.0 since 12.2.2 I believe.
Paul
2018-07-11 18:57 GMT+02:00 Huseyin Cotuk :
> Hi Paul,
>
> Thanks for your reply. I did not mention any special parameter while
> upgrading to luminous. So this ceph-deploy version is the one coming from
> the official debia
Hi Paul,
Thanks for your reply. I did not mention any special parameter while upgrading
to luminous. So this ceph-deploy version is the one coming from the official
debian luminous repo.
I will try to downgrade ceph-deploy and try to add osd again. To prevent any
inconsistency, maybe you can c
BlueStore is really stable and mature nowadays.
You seem to be using ceph-deploy 2.0.0 which I would not call mature and
stable at the moment ;)
Anyways, it uses ceph-volume instead of ceph-disk and I think you have to
specify the actual partition here.
But I'd just downgrade to ceph-deploy 1.5.39
