Bug 1366036
| Summary: | Unable to create striped raid on VGs with 1k extent sizes... again | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Heinz Mauelshagen <heinzm> |
| lvm2 sub component: | Mirroring and RAID | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | unspecified | CC: | agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, zkabelac |
| Version: | 7.3 | Keywords: | Regression |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.171-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 21:47:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1179970 | ||
|
Description
Corey Marthaler
2016-08-10 20:08:49 UTC
Forgot about the issues mentioned in 1179970: https://bugzilla.redhat.com/show_bug.cgi?id=1179970#c7 This is a dup of that. So we're looking at a general LV-level restriction here. Page sizes differ, and we expect VGs to work on different machines. We also expect to be able mix-and-match LV types within a VG regardless of VG extent size. The kernel raid code imposes a page size restriction. What we can do is take the worst case of this and impose it on the creation of (or conversion to) raid LVs. Existing LVs would be unaffected (insofar as they already work). (Any alignment problems giving non-optimal allocation layouts should be a wider issue that should be addressed separately.) I got patch fixing this up including to make sure that the MetaLVs have decent minimum size. Unlikely to make it into 7.3 because of lag of review/testing. I'm passing this on to rhel7.4. I don't believe this regression qualifies as a blocker. People should not be creating VGs with PEs that are more than 3 orders of magnitude smaller than the default. No-one uses floppy disks anymore. I have no problem waiting on this one. (In reply to Jonathan Earl Brassow from comment #6) > I'm passing this on to rhel7.4. I don't believe this regression qualifies > as a blocker. People should not be creating VGs with PEs that are more than > 3 orders of magnitude smaller than the default. No-one uses floppy disks > anymore. I have no problem waiting on this one. For the same reason, I am pulling the blocker flag. lvm2 2.02.16 # vgs --noh -oname,extentsize nvm nvm 1.00k # lvcreate --ty raid0_meta -L500 -i2 -nr nvm Using default stripesize 64.00 KiB. Unable to create RAID LV: requires minimum VG extent size 4.00 KiB lvm2 2.02.169 that is Upstream commit 73df2aedf9788dcf2dbf09f20f8783c6d2108e75 in lvm2 since version 2.02.165 Verified that all (striped and mirrored) raid create attempts now fail on 1k extent sized VGs, yet pass when attempted on 4k extent sized VGs. 3.10.0-660.el7.x86_64 lvm2-2.02.171-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 lvm2-libs-2.02.171-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 lvm2-cluster-2.02.171-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 device-mapper-1.02.140-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 device-mapper-libs-1.02.140-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 device-mapper-event-1.02.140-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 device-mapper-event-libs-1.02.140-1.el7 BUILT: Wed May 3 07:05:13 CDT 2017 device-mapper-persistent-data-0.7.0-0.1.rc6.el7 BUILT: Mon Mar 27 10:15:46 CDT 2017 # 1k vg attempt [root@host-126 ~]# vgcreate -s 1K raid_sanity /dev/sda1 /dev/sda2 /dev/sdc1 /dev/sdc2 /dev/sdd1 /dev/sdd2 /dev/sdf1 /dev/sdf2 /dev/sdh1 /dev/sdh2 Volume group "raid_sanity" successfully created [root@host-126 ~]# lvcreate --type raid1 -m 1 -n raid_on_1Kextent_vg -L 20M raid_sanity Unable to create RAID LV: requires minimum VG extent size 4.00 KiB # 4k vg attempt [root@host-126 ~]# vgcreate -s 4K raid_sanity /dev/sda1 /dev/sda2 /dev/sdb1 /dev/sdb2 /dev/sde1 /dev/sde2 /dev/sdf1 /dev/sdf2 /dev/sdg1 /dev/sdg2 Volume group "raid_sanity" successfully created [root@host-126 ~]# lvcreate --type raid1 -m 1 -n raid_on_4Kextent_vg -L 20M raid_sanity Logical volume "raid_on_4Kextent_vg" created. [root@host-126 ~]# lvs -a -o +devices LV VG Attr LSize Cpy%Sync Devices raid_on_4Kextent_vg raid_sanity rwi-a-r--- 20.00m 100.00 raid_on_4Kextent_vg_rimage_0(0),raid_on_4Kextent_vg_rimage_1(0) [raid_on_4Kextent_vg_rimage_0] raid_sanity iwi-aor--- 20.00m /dev/sda1(3) [raid_on_4Kextent_vg_rimage_1] raid_sanity iwi-aor--- 20.00m /dev/sda2(3) [raid_on_4Kextent_vg_rmeta_0] raid_sanity ewi-aor--- 12.00k /dev/sda1(0) [raid_on_4Kextent_vg_rmeta_1] raid_sanity ewi-aor--- 12.00k /dev/sda2(0) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2222 |