all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Marco Witte <m.witte@neusta.de>
To: <pve-user@lists.proxmox.com>
Subject: [PVE-User] proxmox ceph osd option to move wal to a new device
Date: Wed, 12 Jan 2022 14:57:51 +0100	[thread overview]
Message-ID: <2a32d0af-d323-f38d-cbf6-6a11ba16c452@neusta.de> (raw)

One wal drive was failing. So I replaced it with:
pveceph osd destroy 17 --cleanup 1
pveceph osd destroy 18 --cleanup 1
pveceph osd destroy 19 --cleanup 1

This removed the three disks and removed the osd-wal.

The Drive sdf is the replacement for the failed wal device that above 
three osds ( sdb, sdc,sdd ) used:
pveceph osd create /dev/sdb -wal_dev /dev/sdf
pveceph osd create /dev/sdc -wal_dev /dev/sdf
pveceph osd create /dev/sdd -wal_dev /dev/sdf

This approach worked fine, but took a lot of time.

So I figured it would be better to change the wal for the existing osd:
At this state /dev/sdf is completly empty (has no lvm/wiped) and all 
three osd still use the failing wal device /dev/sdh.

ceph-volume lvm new-wal --osd-id 17 --osd-fsid 
01234567-1234-1234-123456789012 --target /dev/sdf

Which obviously fails, because the target should be --target vgname/new_wal

Question part:
What would be the fast way to make the new device /dev/sdf the wal 
device, without destroying the osds 17 18 19?

Versions:
pve-manager/7.1-8/5b267f33 (running kernel: 5.13.19-2-pve)
ceph version 16.2.7 (f9aa029788115b5df5eeee328f584156565ee5b7) pacific 
(stable)

Thank you





             reply	other threads:[~2022-01-12 14:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 13:57 Marco Witte [this message]
     [not found] <5eaaf695-e2fd-bef1-3f1e-a6a2fc89acdf@neusta.de>
     [not found] ` <mailman.36.1642149278.436.pve-user@lists.proxmox.com>
2022-01-14 11:50   ` Marco Witte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a32d0af-d323-f38d-cbf6-6a11ba16c452@neusta.de \
    --to=m.witte@neusta.de \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal