Remove separate WAL device from OSD
Hi, Is it possible to remove an existing WAL device from an OSD? I saw that ceph-bluestore-tool has a command bluefs-bdev-migrate, but it's not clear to me if this can only move a WAL device or if it can be used to remove it ... Regards, Michael
Hello, isnt ceph-osd -i osdnum... –flush-journal and then removing the journal enough? On 22.09.20 21:09, Michael Fladischer wrote:
Hi,
Is it possible to remove an existing WAL device from an OSD? I saw that ceph-bluestore-tool has a command bluefs-bdev-migrate, but it's not clear to me if this can only move a WAL device or if it can be used to remove it ...
Regards, Michael _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Andreas John net-lab GmbH | Frankfurter Str. 99 | 63067 Offenbach Geschaeftsfuehrer: Andreas John | AG Offenbach, HRB40832 Tel: +49 69 8570033-1 | Fax: -2 | http://www.net-lab.net Facebook: https://www.facebook.com/netlabdotnet Twitter: https://twitter.com/netlabdotnet
Hi, I don't think there's a way to remove WAL/DB without rebuilding the OSD. ceph-bluestore-tool bluefs-bdev-migrate expects a target device to migrate the data since it's a migration. I can't read the full thread (I get a server error), what is the goal here? Regards, Eugen Zitat von Michael Fladischer <michael@fladi.at>:
Hi Andreas,
Am 22.09.2020 um 22:35 schrieb Andreas John:
and then removing the journal enough?
any hints on how to remove the journal?
Regards, Michael _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Hi Eugen, Am 23.09.2020 um 14:51 schrieb Eugen Block:
I don't think there's a way to remove WAL/DB without rebuilding the OSD. ceph-bluestore-tool bluefs-bdev-migrate expects a target device to migrate the data since it's a migration. I can't read the full thread (I get a server error), what is the goal here?
the goal is simply to remove the WAL from an OSD so that it only uses the primary block device (HDD). They were created with a separate WAL device (on SSD) and I would like to use the current WAL device as a spearate DB instead. I'll resort to recreating the OSDs if there is no way to remove the WAL. Regards, Michael
Hi Michael, yes, you can use ceph-bluestore-tool to do that. E.g. bin/ceph-bluestore-tool --path dev/osd0 --devs-source dev/osd0/block.wal --dev-target dev/osd0/block.db --command bluefs-bdev-migrate inferring bluefs devices from bluestore path device removed:0 dev/osd0/block.wal Additionally you might probably need to zap wal device with ceph-volume after the migration to avoid its attachment to OSD on node restart. Not completely sure about that though... Thanks, Igor On 9/22/2020 10:09 PM, Michael Fladischer wrote:
Hi,
Is it possible to remove an existing WAL device from an OSD? I saw that ceph-bluestore-tool has a command bluefs-bdev-migrate, but it's not clear to me if this can only move a WAL device or if it can be used to remove it ...
Regards, Michael _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Hi Igor, Am 23.09.2020 um 18:38 schrieb Igor Fedotov:
bin/ceph-bluestore-tool --path dev/osd0 --devs-source dev/osd0/block.wal --dev-target dev/osd0/block.db --command bluefs-bdev-migrate
Would this also work if the OSD only has its primary block device and the separate WAL device? Like running: ceph-bluestore-tool --path dev/osd0 --devs-source dev/osd0/block.wal \ --dev-target dev/osd0/block --command bluefs-bdev-migrate
Additionally you might probably need to zap wal device with ceph-volume after the migration to avoid its attachment to OSD on node restart. Not completely sure about that though...
Since the WAL device is just a LV I'd remove the LV once the OSD is back up and in. Thanks, Michael
Yeah, this should work as well... On 9/24/2020 9:32 AM, Michael Fladischer wrote:
Hi Igor,
Am 23.09.2020 um 18:38 schrieb Igor Fedotov:
bin/ceph-bluestore-tool --path dev/osd0 --devs-source dev/osd0/block.wal --dev-target dev/osd0/block.db --command bluefs-bdev-migrate
Would this also work if the OSD only has its primary block device and the separate WAL device? Like running:
ceph-bluestore-tool --path dev/osd0 --devs-source dev/osd0/block.wal \ --dev-target dev/osd0/block --command bluefs-bdev-migrate
Additionally you might probably need to zap wal device with ceph-volume after the migration to avoid its attachment to OSD on node restart. Not completely sure about that though...
Since the WAL device is just a LV I'd remove the LV once the OSD is back up and in.
Thanks, Michael _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (4)
-
Andreas John
-
Eugen Block
-
Igor Fedotov
-
Michael Fladischer