Bug 1985112 - Scrubbing not possible on RAID5 with 3 LUKS SSDs
Summary: Scrubbing not possible on RAID5 with 3 LUKS SSDs
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Heinz Mauelshagen
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-22 22:12 UTC by nc-duenkekl3
Modified: 2023-08-10 15:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
pm-rhel: lvm-technical-solution?
pm-rhel: lvm-test-coverage?


Attachments (Terms of Use)

Description nc-duenkekl3 2021-07-22 22:12:26 UTC
Description of problem:
I can't scrub (check / repair) the raid.

Version-Release number of selected component (if applicable):
LVM2 2.03.12

How reproducible:
Every time.

Steps to Reproduce:
1. Create a LUKS fulldisk partition on each of the 3 SSDs
2. Use LVM to create a RAID 5
3. Format the new RAID5 partition with BTRFS
4. Execute sudo lvchange --syncaction check cryptdata_raid5/home

Actual results:
Command on LV cryptdata_raid5/home does not accept LV type linear.
Command not permitted on LV cryptdata_raid5/home.


Expected results:
Checking and repairing.

Additional info:
Do I need to use MDADM to make a RAID5 first and use the MDADM tools for scrubbing?
The arch wiki said it's perfectly fine to create a RAID5 via LVM directly.

Comment 1 Heinz Mauelshagen 2021-11-03 12:45:53 UTC
Would be valuable to confirm, that an MD array vs. the LVM RAID5 LV behaves differently relative to scrubbing but LVM should actually allow scrubbing on the RaidLV.  I.e. the stack 3x LUKS -> MD RAID5 array -> BTRFS allows for scrubbing.


Note You need to log in before you can comment on or make changes to this bug.