Just to follow up...
I was able to use a per-osd device copy to migrate nearly 80 FileStore
osds to BlueStore using a version of the script in:
https://tracker.ceph.com/issues/47839
Cheers,
Chris
On Fri, Oct 09, 2020 at 12:05:32PM +1100, Chris Dunlop wrote:
Hi,
The docs have scant detail
Hi Anthony,
Thanks for looking into this and opening the ticket - I'll keep an eye on it.
For prepping the LVMs etc. I was thinking could probably use 'ceph-volume
lvm prepare' then fixing up the relevant LV tags with the appropriate values
from the origin osd.
Cheers,
Chris
On Mon, Oct 12
Poking through the source I *think* the doc should indeed refer to the “dup”
function, vs “copy”. That said, arguably we shouldn’t have a section in the
docs that says "there’s this thing you can do but we aren’t going to tell you
how”.
Looking at the history / blame info, which only seems to
I really should read these emails more carefully... Sorry, thanks for
pointing that out. I haven't done the filestore migration per OSD. I
created a filestore OSD in my lab setup to play around with
ceph-objectstore-tool but I couldn't find anything except for '--op
dup' but it's not really
Hi Eugen,
Reminder: I'm looking for guidance / hints on how to migrate from
filestore to bluestore using a "per-osd device copy":
https://docs.ceph.com/en/latest/rados/operations/bluestore-migration/#per-osd-device-copy
On Fri, Oct 09, 2020 at 07:03:33AM +, Eugen Block wrote:
I think by "
Hi,
I think by "copy function" would be the "bluefs-bdev-migrate" command
from ceph-bluestore-tool, this is an excerpt from the man paage:
---snip---
bluefs-bdev-migrate --dev-target new-device --devs-source device1
[--devs-source device2]
Moves BlueFS data from source device
