linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Roger James <roger@beardandsandals.co.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Recovering from a failed pvmove
Date: Tue, 28 Jun 2022 09:30:22 +0100	[thread overview]
Message-ID: <181a96ed530.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk> (raw)
In-Reply-To: <181a3eed7e0.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk>


[-- Attachment #1.1: Type: text/plain, Size: 4803 bytes --]

I have now managed to fix the problem. I ran vgcfgbackup, then made a copy 
of the backup for safety purposes. I than hand edited the original backup 
to remove the missing pv (pv4), the root lv and the pvmove0 lv. I then than 
vgcfgrestore. Everything is working.

There must be a better way of doing this. Hand editing cfg files is not 
safe or sensible. What have I missed?

Roger

On 28 June 2022 07:38:48 Roger James <roger@beardandsandals.co.uk> wrote:
> Hi,
>
> I am struggling to recover from a failed pvmove. Unfortunately I only have 
> a limited knowledge of lvm. I setup my lvm configuration many years ago.
>
> I was trying to move a lv to a SSD using pvmove. Unfortunately my brand new 
> SSD choose that moment to fail (never buy cheap SSDs, lesson learnt!").
>
> This is the current status.
>
> roger@dragon:~$ sudo pvs
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> PV VG Fmt Attr PSize PFree
> /dev/sda1 wd lvm2 a-- <465.76g 0
> /dev/sdb1 wd lvm2 a-- <465.76g <80.45g
> /dev/sdc2 wd lvm2 a-- 778.74g 278.74g
> /dev/sdd1 wd lvm2 a-- <465.76g 0
> [unknown] wd lvm2 a-m <784.49g 685.66g
> roger@dragon:~$ sudo lvs
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
> home wd -wi------- 1.46t
> root wd -wI-----p- <108.83g
> swap wd -wi------- 8.00g
> work wd -wi------- 200.00g
> roger@dragon:~$ sudo vgs
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> VG #PV #LV #SN Attr VSize VFree
> wd 5 4 0 wz-pn- 2.89t 1.02t
>
> This is a recap of what I have tried so far.
>
> roger@dragon:~$ sudo pvmove --abort
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> LVM command executed by lvmpolld failed.
> For more information see lvmpolld messages in syslog or lvmpolld log file.
> roger@dragon:~$ sudo vgreduce --removemissing wd
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: Partial LV root needs to be repaired or removed.
> WARNING: Partial LV pvmove0 needs to be repaired or removed.
> There are still partial LVs in VG wd.
> To remove them unconditionally use: vgreduce --removemissing --force.
> To remove them unconditionally from mirror LVs use: vgreduce 
> --removemissing --mirrorsonly --force.
> WARNING: Proceeding to remove empty missing PVs.
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> roger@dragon:~$ sudo lvchange -an wd/root
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> roger@dragon:~$ sudo vgreduce --removemissing wd
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: Partial LV root needs to be repaired or removed.
> WARNING: Partial LV pvmove0 needs to be repaired or removed.
> There are still partial LVs in VG wd.
> To remove them unconditionally use: vgreduce --removemissing --force.
> To remove them unconditionally from mirror LVs use: vgreduce 
> --removemissing --mirrorsonly --force.
> WARNING: Proceeding to remove empty missing PVs.
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> roger@dragon:~$ sudo lvremove wd/pvmove0
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> WARNING: VG wd is missing PV uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ (last 
> written to [unknown]).
> WARNING: Couldn't find device with uuid uMtjop-PmMT-603f-GWWQ-fR4f-s4Sw-XSKNXZ.
> Can't remove locked logical volume wd/pvmove0.
>
> I am quite happy to loose the root lv, I just need the home and work lvs. 
> What am I missing?
>
> Help!
>
> Roger
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://listman.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[-- Attachment #1.2: Type: text/html, Size: 8397 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2022-06-29  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  6:52 [linux-lvm] Recovering from a failed pvmove Roger James
2022-06-28  8:30 ` Roger James [this message]
2022-06-29 11:05   ` Roger Heflin
2022-06-28 18:12 ` Roger Heflin

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=181a96ed530.27a5.d4b3b9aee17a85f6bc878c68b3925db6@beardandsandals.co.uk \
    --to=roger@beardandsandals.co.uk \
    --cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).