From: "Andreas Schrägle" <linux-lvm@ajs124.de>
To: Adam Puleo <adam.puleo@icloud.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Replace Drive in RAID6
Date: Wed, 3 Nov 2021 15:25:58 +0100 [thread overview]
Message-ID: <20211103152558.7670fa10@desk> (raw)
In-Reply-To: <1495660C-B6EF-4315-8599-F79F7B6CCF73@icloud.com>
On Tue, 2 Nov 2021 22:56:18 -0700
Adam Puleo <adam.puleo@icloud.com> wrote:
> Hello,
>
> One of my drives failed in my RAID6 and I’m trying to replace it without success.
>
> I’m trying to rebuild the failed drive (/dev/sda): lvchange --rebuild /dev/sda vg_data
>
> But I’m receiving the error: vg_data/lv_data must be active to perform this operation.
>
> I have tried to activate the logical volume without success.
>
> How do I go about activating the volume so that I can rebuild the failed drive?
>
> Thanks,
> -Adam
>
> # lvs -a -o name,segtype,devices
> LV Type Devices
> lv_data raid6 lv_data_rimage_0(0),lv_data_rimage_1(0),lv_data_rimage_2(0),lv_data_rimage_3(0),lv_data_rimage_4(0)
> [lv_data_rimage_0] error
> [lv_data_rimage_1] linear /dev/sdc1(1)
> [lv_data_rimage_2] linear /dev/sdb1(1)
> [lv_data_rimage_3] linear /dev/sdf1(1)
> [lv_data_rimage_4] linear /dev/sde1(2)
> [lv_data_rmeta_0] error
> [lv_data_rmeta_1] linear /dev/sdc1(0)
> [lv_data_rmeta_2] linear /dev/sdb1(0)
> [lv_data_rmeta_3] linear /dev/sdf1(0)
> [lv_data_rmeta_4] linear /dev/sde1(0)
>
> # lvs -a
> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
> lv_data vg_data rwi---r--- 990.00g
> [lv_data_rimage_0] vg_data vwi-a-r-r- 330.00g
> [lv_data_rimage_1] vg_data Iwi-a-r-r- 330.00g
> [lv_data_rimage_2] vg_data Iwi-a-r-r- 330.00g
> [lv_data_rimage_3] vg_data Iwi-a-r-r- 330.00g
> [lv_data_rimage_4] vg_data Iwi-a-r-r- 330.00g
> [lv_data_rmeta_0] vg_data ewi-a-r-r- 4.00m
> [lv_data_rmeta_1] vg_data ewi-a-r-r- 4.00m
> [lv_data_rmeta_2] vg_data ewi-a-r-r- 4.00m
> [lv_data_rmeta_3] vg_data ewi-a-r-r- 4.00m
> [lv_data_rmeta_4] vg_data ewi-a-r-r- 4.00m
>
>
>
> _______________________________________________
> 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/
Hello Adam,
how exactly have you tried to activate the LV so far?
lvchange with --activationmode degraded should work, no?
Also, are you sure that --rebuild is the correct operation?
man 7 lvmraid suggest you might want --repair or --replace instead.
Best Regards
_______________________________________________
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/
next prev parent reply other threads:[~2021-11-04 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 5:56 [linux-lvm] Replace Drive in RAID6 Adam Puleo
2021-11-03 6:41 ` Roberto Fastec
2021-11-03 14:25 ` Andreas Schrägle [this message]
2021-11-05 2:21 ` Adam Puleo
2021-11-08 7:06 ` Adam Puleo
2021-11-16 17:41 ` Heinz Mauelshagen
2021-11-16 17:46 ` Heinz Mauelshagen
2021-11-20 7:15 ` Adam Puleo
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=20211103152558.7670fa10@desk \
--to=linux-lvm@ajs124.de \
--cc=adam.puleo@icloud.com \
--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).