Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1842705

Summary: lvmdbusd needs to learn about integrity 'g' lv_attr
Product: Red Hat Enterprise Linux 8 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: David Teigland <teigland>
lvm2 sub component: lvmdbusd QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: agk, heinzm, jbrassow, mcsontos, msnitzer, pasik, prajnoha, tasleson, zkabelac
Version: 8.3Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.03.09-4.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 02:00:38 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:

Description Corey Marthaler 2020-06-01 21:48:52 UTC
Description of problem:

[root@hayes-03 ~]# lvcreate --yes  --type raid1 -m 1 -n raid_up_converts -L 100M --raidintegrity y --raidintegritymode journal raid_sanity
  Creating integrity metadata LV raid_up_converts_rimage_0_imeta with size 4.00 MiB.
  Logical volume "raid_up_converts_rimage_0_imeta" created.
  Creating integrity metadata LV raid_up_converts_rimage_1_imeta with size 4.00 MiB.
  Logical volume "raid_up_converts_rimage_1_imeta" created.
  Wiping xfs_external_log signature on /dev/raid_sanity/raid_up_converts.
  Wiping xfs_external_log signature on /dev/raid_sanity/raid_up_converts.
  Wiping xfs_external_log signature on /dev/raid_sanity/raid_up_converts.
  Wiping xfs_external_log signature on /dev/raid_sanity/raid_up_converts.
  Logical volume "raid_up_converts" created.

[root@hayes-03 ~]# lvs
  LV               VG          Attr       LSize   Origin Data%  Meta%  Move Log Cpy%Sync
  raid_up_converts raid_sanity rwi-a-r--- 100.00m                               100.00

[root@hayes-03 ~]# lvs -a -o +devices
  LV                                VG          Attr       LSize   Origin                            Data%  Meta%  Move Log Cpy%Sync Devices
  raid_up_converts                  raid_sanity rwi-a-r--- 100.00m                                                          100.00   raid_up_converts_rimage_0(0),raid_up_converts_rimage_1(0)
  [raid_up_converts_rimage_0]       raid_sanity gwi-aor--- 100.00m [raid_up_converts_rimage_0_iorig]                        100.00   raid_up_converts_rimage_0_iorig(0)
  [raid_up_converts_rimage_0_imeta] raid_sanity ewi-ao----   4.00m                                                                   /dev/sdb1(26)
  [raid_up_converts_rimage_0_iorig] raid_sanity -wi-ao---- 100.00m                                                                   /dev/sdb1(1)
  [raid_up_converts_rimage_1]       raid_sanity gwi-aor--- 100.00m [raid_up_converts_rimage_1_iorig]                        100.00   raid_up_converts_rimage_1_iorig(0)
  [raid_up_converts_rimage_1_imeta] raid_sanity ewi-ao----   4.00m                                                                   /dev/sdc1(26)
  [raid_up_converts_rimage_1_iorig] raid_sanity -wi-ao---- 100.00m                                                                   /dev/sdc1(1)
  [raid_up_converts_rmeta_0]        raid_sanity ewi-aor---   4.00m                                                                   /dev/sdb1(0)
  [raid_up_converts_rmeta_1]        raid_sanity ewi-aor---   4.00m                                                                   /dev/sdc1(0)

Jun  1 16:41:40 hayes-03 lvm[11446]: raid1 array, raid_sanity-raid_up_converts, is now in-sync.
Jun  1 16:41:48 hayes-03 lvmdbusd[2989]: 2989:2989 - LV lag306-OBOS-oEGA-rET1-1gsd-nJgG-emFRuI [raid_up_converts_rimage_0] with lv_attr gwi-aor---, lv_attr[0] = 'g' is not known
Jun  1 16:41:48 hayes-03 lvmdbusd[2989]: 2989:2989 - LV VXJkZR-rUih-h4HF-BjCY-7nN7-40eN-RA1CNc [raid_up_converts_rimage_1] with lv_attr gwi-aor---, lv_attr[0] = 'g' is not known



Version-Release number of selected component (if applicable):
kernel-4.18.0-208.el8    BUILT: Thu May 28 09:44:03 CDT 2020
lvm2-2.03.09-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
lvm2-libs-2.03.09-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
lvm2-dbusd-2.03.09-2.el8    BUILT: Fri May 29 11:32:49 CDT 2020
lvm2-lockd-2.03.09-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
boom-boot-1.1-2.el8    BUILT: Tue May 26 08:45:48 CDT 2020
device-mapper-1.02.171-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
device-mapper-libs-1.02.171-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
device-mapper-event-1.02.171-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
device-mapper-event-libs-1.02.171-2.el8    BUILT: Fri May 29 11:29:58 CDT 2020
device-mapper-persistent-data-0.8.5-3.el8    BUILT: Wed Nov 27 07:05:21 CST 2019

Comment 4 Corey Marthaler 2020-08-17 20:03:29 UTC
Fix verified in the latest rpms.

kernel-4.18.0-232.el8    BUILT: Mon Aug 10 02:17:54 CDT 2020
lvm2-2.03.09-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020
lvm2-libs-2.03.09-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020
lvm2-dbusd-2.03.09-5.el8    BUILT: Wed Aug 12 15:49:44 CDT 2020
lvm2-lockd-2.03.09-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020
device-mapper-1.02.171-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020
device-mapper-libs-1.02.171-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020
device-mapper-event-1.02.171-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020
device-mapper-event-libs-1.02.171-5.el8    BUILT: Wed Aug 12 15:51:50 CDT 2020


[root@hayes-01 ~]# lvcreate --yes  --type raid1 -m 1 -n raid_up_converts -L 100M --raidintegrity y --raidintegritymode journal test
  Creating integrity metadata LV raid_up_converts_rimage_0_imeta with size 8.00 MiB.
  Logical volume "raid_up_converts_rimage_0_imeta" created.
  Creating integrity metadata LV raid_up_converts_rimage_1_imeta with size 8.00 MiB.
  Logical volume "raid_up_converts_rimage_1_imeta" created.
  Logical volume "raid_up_converts" created.
[root@hayes-01 ~]# lvs -a -o +devices
  LV                                VG   Attr       LSize    Origin                            Cpy%Sync Devices
  raid_up_converts                  test rwi-a-r--- 100.00m                                    100.00   raid_up_converts_rimage_0(0),raid_up_converts_rimage_1(0)
  [raid_up_converts_rimage_0]       test gwi-aor--- 100.00m  [raid_up_converts_rimage_0_iorig] 100.00   raid_up_converts_rimage_0_iorig(0)
  [raid_up_converts_rimage_0_imeta] test ewi-ao----   8.00m                                             /dev/sdb1(26)
  [raid_up_converts_rimage_0_iorig] test -wi-ao---- 100.00m                                             /dev/sdb1(1)
  [raid_up_converts_rimage_1]       test gwi-aor--- 100.00m  [raid_up_converts_rimage_1_iorig] 100.00   raid_up_converts_rimage_1_iorig(0)
  [raid_up_converts_rimage_1_imeta] test ewi-ao----   8.00m                                             /dev/sdc1(26)
  [raid_up_converts_rimage_1_iorig] test -wi-ao---- 100.00m                                             /dev/sdc1(1)
  [raid_up_converts_rmeta_0]        test ewi-aor---   4.00m                                             /dev/sdb1(0)
  [raid_up_converts_rmeta_1]        test ewi-aor---   4.00m                                             /dev/sdc1(0)
[root@hayes-01 ~]# grep lv_attr /var/log/messages | grep "is not known"
[root@hayes-01 ~]# 

Aug 17 14:58:59 hayes-01 kernel: device-mapper: raid: Superblocks created for new raid set
Aug 17 14:58:59 hayes-01 kernel: md/raid1:mdX: not clean -- starting background reconstruction
Aug 17 14:58:59 hayes-01 kernel: md/raid1:mdX: active with 2 out of 2 mirrors
Aug 17 14:58:59 hayes-01 kernel: mdX: bitmap file is out of date, doing full recovery
Aug 17 14:58:59 hayes-01 kernel: md: resync of RAID array mdX
Aug 17 14:58:59 hayes-01 lvm[266686]: Monitoring RAID device test-raid_up_converts for events.
Aug 17 14:58:59 hayes-01 dmeventd[266686]: No longer monitoring RAID device test-raid_up_converts for events.
Aug 17 14:58:59 hayes-01 kernel: md: mdX: resync interrupted.
Aug 17 14:58:59 hayes-01 kernel: md/raid1:mdX: not clean -- starting background reconstruction
Aug 17 14:58:59 hayes-01 kernel: md/raid1:mdX: active with 2 out of 2 mirrors
Aug 17 14:59:00 hayes-01 kernel: md: requested-resync of RAID array mdX
Aug 17 14:59:00 hayes-01 lvm[266686]: Monitoring RAID device test-raid_up_converts for events.
Aug 17 14:59:02 hayes-01 kernel: md: mdX: requested-resync done.
Aug 17 14:59:02 hayes-01 lvm[266686]: raid1 array, test-raid_up_converts, is now in-sync.

Comment 7 errata-xmlrpc 2020-11-04 02:00:38 UTC
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 (lvm2 bug fix and enhancement update), 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-2020:4546