linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Adam Niescierowicz <adam.niescierowicz@justnet.pl>
To: linux-lvm@lists.linux.dev
Subject: lvconvert --type raid5 failure
Date: Tue, 22 Oct 2024 17:26:57 +0200	[thread overview]
Message-ID: <1f1681d7-c34e-4f6f-9625-a155b9766eb3@justnet.pl> (raw)

[-- Attachment #1: Type: text/plain, Size: 4269 bytes --]

Hi,

I have LV type raid1 and after adding couple disk to VG I anted to 
change raid1 to raid5 so I did:

 > # lvconvert --type raid5 /dev/first/lxc-owncloud-data-new

it converted LV to RAID5 but didn't add new spare so:

 > # lvconvert --stripes 2 /dev/first/lxc-owncloud-data-new

After this LV have 3 device but I didn't saw any sync action and 
movement on the disk so to resync data I used:

 > # lvchange --resync /dev/first/lxc-owncloud-data-new

It was like conversion from 6 to 12TB so after 40 hours when resync was 
done I do mount and XFS complain about FS.

What I did wrong?
Is there a chance that I can recover data?


 From LVM Archive

> # Orginal LV
> lxc-owncloud-data-new {
>     id = "4D3gRF-19uK-kCTX-DaYS-tmEx-Egs5-zRs7xp"
>     status = ["READ", "WRITE", "VISIBLE"]
>     flags = []
>     creation_time = 1713726446  # 2024-04-21 21:07:26 +0200
>     creation_host = "lxc4"
>     segment_count = 1
>
>     segment1 {
>         start_extent = 0
>         extent_count = 1572864  # 6 Terabytes
>
>         type = "raid1"
>         device_count = 2
>         region_size = 8192
>
>         raids = [
>             "lxc-owncloud-data-new_rmeta_0", 
> "lxc-owncloud-data-new_rimage_0",
>             "lxc-owncloud-data-new_rmeta_1", 
> "lxc-owncloud-data-new_rimage_1"
>         ]
>     }
> }
>
>
> # After lvconvert --type raid5 /dev/first/lxc-owncloud-data-new
> lxc-owncloud-data-new {
>     id = "4D3gRF-19uK-kCTX-DaYS-tmEx-Egs5-zRs7xp"
>     status = ["READ", "WRITE", "VISIBLE"]
>     flags = []
>     creation_time = 1713726446  # 2024-04-21 21:07:26 +0200
>     creation_host = "lxc4"
>     segment_count = 1
>
>     segment1 {
>         start_extent = 0
>         extent_count = 1572864  # 6 Terabytes
>
>         type = "raid5"
>         device_count = 2
>         region_size = 8192
>         stripe_size = 128
>
>         raids = [
>             "lxc-owncloud-data-new_rmeta_0", 
> "lxc-owncloud-data-new_rimage_0",
>             "lxc-owncloud-data-new_rmeta_1", 
> "lxc-owncloud-data-new_rimage_1"
>         ]
>     }
> }
>
>
> # After lvconvert --stripes 2 /dev/first/lxc-owncloud-data-new
> lxc-owncloud-data-new {
>     id = "4D3gRF-19uK-kCTX-DaYS-tmEx-Egs5-zRs7xp"
>     status = ["READ", "WRITE", "VISIBLE"]
>     flags = []
>     creation_time = 1713726446  # 2024-04-21 21:07:26 +0200
>     creation_host = "lxc4"
>     segment_count = 1
>
>     segment1 {
>         start_extent = 0
>         extent_count = 3145730  # 12 Terabytes
>
>         reshape_count = 1   # 4 Megabytes
>         type = "raid5"
>         device_count = 3
>         region_size = 16384
>         stripe_size = 128
>
>         raids = [
>             "lxc-owncloud-data-new_rmeta_0", 
> "lxc-owncloud-data-new_rimage_0",
>             "lxc-owncloud-data-new_rmeta_1", 
> "lxc-owncloud-data-new_rimage_1",
>             "lxc-owncloud-data-new_rmeta_2", 
> "lxc-owncloud-data-new_rimage_2"
>         ]
>     }
> }
>
> # Didn't have progress of reshape in LVS
>
> lxc-owncloud-data-new {
>     id = "4D3gRF-19uK-kCTX-DaYS-tmEx-Egs5-zRs7xp"
>     status = ["READ", "WRITE", "VISIBLE"]
>     flags = []
>     creation_time = 1713726446  # 2024-04-21 21:07:26 +0200
>     creation_host = "lxc4"
>     segment_count = 1
>
>     segment1 {
>         start_extent = 0
>         extent_count = 3145728  # 12 Terabytes
>
>         type = "raid5"
>         device_count = 3
>         region_size = 16384
>         stripe_size = 128
>
>         raids = [
>             "lxc-owncloud-data-new_rmeta_0", 
> "lxc-owncloud-data-new_rimage_0",
>             "lxc-owncloud-data-new_rmeta_1", 
> "lxc-owncloud-data-new_rimage_1",
>             "lxc-owncloud-data-new_rmeta_2", 
> "lxc-owncloud-data-new_rimage_2"
>         ]
>     }
> }
>
> # lvchange --resync /dev/first/lxc-owncloud-data-new


-- 
---
Pozdrawiam
Adam Nieścierowicz

[-- Attachment #2: adam_niescierowicz.vcf --]
[-- Type: text/vcard, Size: 195 bytes --]

begin:vcard
fn;quoted-printable:Adam Nie=C5=9Bcierowicz
n;quoted-printable:Nie=C5=9Bcierowicz;Adam
email;internet:adam.niescierowicz@justnet.pl
x-mozilla-html:TRUE
version:2.1
end:vcard


             reply	other threads:[~2024-10-22 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 15:26 Adam Niescierowicz [this message]
2024-10-22 17:59 ` lvconvert --type raid5 failure Adam Niescierowicz

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=1f1681d7-c34e-4f6f-9625-a155b9766eb3@justnet.pl \
    --to=adam.niescierowicz@justnet.pl \
    --cc=linux-lvm@lists.linux.dev \
    /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).