| Summary: | pvcreate on a dev with existing MD signature confuses .cache | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Nenad Peric <nperic> |
| Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
| lvm2 sub component: | Devices, Filtering and Stacking (RHEL6) | QA Contact: | Cluster QE <mspqa-list> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, prockai, tlavigne, zkabelac |
| Version: | 6.6 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.109-2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
If pvcreate is run against a device with an existing MD signature, the device is now correctly made available for immediate use after the signature is wiped. Sometimes previously the device continued to be filtered out, as if the signature had not been wiped.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 08:25:50 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: | |
|
Description
Nenad Peric
2014-08-12 14:59:41 UTC
Well, I've managed to reproduce with non-clustered mode too. So changing the summary. The thing that confused me here was that pvs called after pvcreate recreated the .cache corerctly, while vgs does not recreate the .cache.
[root@rhel6-b ~]# dd if=/dev/zero of=/dev/sda bs=1M
dd: writing `/dev/sda': No space left on device
129+0 records in
128+0 records out
134217728 bytes (134 MB) copied, 0.602169 s, 223 MB/s
[root@rhel6-b ~]# dd if=/dev/zero of=/dev/sdb bs=1M
dd: writing `/dev/sdb': No space left on device
129+0 records in
128+0 records out
134217728 bytes (134 MB) copied, 0.629256 s, 213 MB/s
[root@rhel6-b ~]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup" using metadata type lvm2
[root@rhel6-b ~]# mdadm --create /dev/md0 -l1 --raid-devices 2 /dev/sda /dev/sdb
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
[root@rhel6-b ~]# mdadm -S /dev/md0
mdadm: stopped /dev/md0
[root@rhel6-b ~]# pvcreate /dev/sda
WARNING: software RAID md superblock detected on /dev/sda. Wipe it? [y/n]: y
Wiping software RAID md superblock on /dev/sda.
Physical volume "/dev/sda" successfully created
[root@rhel6-b ~]# cat /etc/lvm/cache/.cache
# This file is automatically maintained by lvm.
persistent_filter_cache {
valid_devices=[
"/dev/disk/by-id/scsi-360000000000000000e00000000020001",
"/dev/disk/by-id/wwn-0x60000000000000000e00000000020001",
"/dev/block/8:0",
"/dev/disk/by-path/ip-192.168.122.1:3260-iscsi-iqn.2012-07.com.redhat.brq.alatyr.virt:host.target_rhel6-lun-1",
"/dev/sda"
]
}
Same problem if you respond 'no' to the 'wipe' confirmation prompt.
This probably dates back to this fix:
commit acb4b5e4de3c49d36fe756f6fb9997ec179b89c2
Author: Milan Broz <mbroz>
Date: Wed Mar 17 14:44:18 2010 +0000
Fix pvcreate device check.
If user try to vgcreate or vgextend non-existent VG,
these messages appears:
# vgcreate xxx /dev/xxx
Internal error: Volume Group xxx was not unlocked
Device /dev/xxx not found (or ignored by filtering).
Unable to add physical volume '/dev/xxx' to volume group 'xxx'.
Internal error: Attempt to unlock unlocked VG xxx.
(the same with existing VG and non-existing PV & vgextend)
# vgextend vg_test /dev/xxx
...
It is caused because code tries to "refresh" cache if
md filter is switched on using cache destroy.
But we can change filters and rescan even without this
machinery now, just use refresh_filters
(and reset md filter afterwards).
(Patch also discovers cache alias bug in vgsplit test,
fix it by using better filter line.)
Fix applied upstream: https://www.redhat.com/archives/lvm-devel/2014-August/msg00019.html [root@virt-065 ~]# mdadm -S /dev/md/md1 mdadm: stopped /dev/md/md1 [root@virt-065 ~]# vgcreate two /dev/sdc1 /dev/sdd1 /dev/sdf1 WARNING: software RAID md superblock detected on /dev/sdc1. Wipe it? [y/n]: y Wiping software RAID md superblock on /dev/sdc1. Incorrect metadata area header checksum on /dev/sdc1 at offset 4096 WARNING: software RAID md superblock detected on /dev/sdd1. Wipe it? [y/n]: y Wiping software RAID md superblock on /dev/sdd1. Incorrect metadata area header checksum on /dev/sdd1 at offset 4096 Physical volume "/dev/sdc1" successfully created Physical volume "/dev/sdd1" successfully created Clustered volume group "two" successfully created [root@virt-065 ~]# vgs VG #PV #LV #SN Attr VSize VFree two 3 0 0 wz--nc 44.99g 44.99g vg_virt065 1 2 0 wz--n- 7.51g 0 The old VGs no longer vanish Marking VERIFIED with: lvm2-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 lvm2-libs-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 lvm2-cluster-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 udev-147-2.57.el6 BUILT: Thu Jul 24 15:48:47 CEST 2014 device-mapper-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-libs-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-event-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-event-libs-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-persistent-data-0.3.2-1.el6 BUILT: Fri Apr 4 15:43:06 CEST 2014 cmirror-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 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. http://rhn.redhat.com/errata/RHBA-2014-1387.html |