With filestore, if the NVMe actually died and you were unable to flush the
journal to the data part of the OSD, then you lost the full OSD as well.
That part hasn't changed at all from filestore to bluestore. There have
been some other tickets on the ML here that talk about using `dd` to
replace
With data located on the OSD (recovery) or as fresh formatted OSD?
Thank you.
With bluestore NVMe frontend is a part of osd. When frontend dies -
backend without db is a junk of bytes.
k
___
ceph-users mailing list
ceph-users@lists.ceph.com
As fresh formatted OSD. All data lost if NVMe dies...
On Thu, Apr 26, 2018 at 1:39 PM, Kevin Olbrich wrote:
>>>What happens im the NVMe dies?
>
>>You lost OSDs backed by that NVMe and need to re-add them to cluster.
>
> With data located on the OSD (recovery) or as fresh formatted
>>What happens im the NVMe dies?
>You lost OSDs backed by that NVMe and need to re-add them to cluster.
With data located on the OSD (recovery) or as fresh formatted OSD?
Thank you.
- Kevin
2018-04-26 12:36 GMT+02:00 Serkan Çoban :
> >On bluestore, is it safe to move
>On bluestore, is it safe to move both Block-DB and WAL to this journal NVMe?
Yes, just specify block-db with ceph-volume and wal also use that
partition. You can put 12-18 HDDs per NVMe
>What happens im the NVMe dies?
You lost OSDs backed by that NVMe and need to re-add them to cluster.
On Thu,
Hi!
On a small cluster I have an Intel P3700 as the journaling device for 4
HDDs.
While using filestore, I used it as journal.
On bluestore, is it safe to move both Block-DB and WAL to this journal NVMe?
Easy maintenance is first priority (on filestore we just had to flush and
replace the SSD).