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 1418054 - pvscan segfault when attempting to scan while underline devices were being repartitioned
Summary: pvscan segfault when attempting to scan while underline devices were being re...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.9
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-31 17:44 UTC by Corey Marthaler
Modified: 2017-12-06 11:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:49:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Corey Marthaler 2017-01-31 17:44:33 UTC 
Description of problem:
Core was generated by `pvscan'.
Program terminated with signal 11, Segmentation fault.


#0  __strncpy_sse2 (s1=0x7ffcacd3a17f "", s2=0x80 <Address 0x80 out of bounds>, n=32) at ./strncpy.c:42
#1  0x00007f5f8925dada in lvmcache_info_from_pvid (pvid=<value optimized out>, valid_only=0) at /usr/include/bits/string3.h:121
#2  0x00007f5f892a990d in _check_or_repair_pv_ext (cmd=<value optimized out>, vgname=<value optimized out>, vgid=0x7f5f00000000 <Address 0x7f5f00000000 out of bounds>, warn_flags=2341128336, 
    consistent=<value optimized out>, precommitted=0) at metadata/metadata.c:3752
#3  _vg_read (cmd=<value optimized out>, vgname=<value optimized out>, vgid=0x7f5f00000000 <Address 0x7f5f00000000 out of bounds>, warn_flags=2341128336, consistent=<value optimized out>, precommitted=0)
    at metadata/metadata.c:4308
#4  0x00007f5f892ad0a8 in vg_read_internal (cmd=<value optimized out>, vgname=0x7f5f8ab0a068 "black_bird", vgid=<value optimized out>, warn_flags=1, consistent=0x7ffcacd3a418) at metadata/metadata.c:4461
#5  0x00007f5f892ad9ad in _recover_vg (cmd=0x7f5f8aac4110, vg_name=0x7f5f8ab0a068 "black_bird", vgid=0x7f5f8ab0a040 "7pu2Bz49SSojNDmv0l9F9qqR79Zlor2w", read_flags=262144, lockd_state=<value optimized out>)
    at metadata/metadata.c:5189
#6  _vg_lock_and_read (cmd=0x7f5f8aac4110, vg_name=0x7f5f8ab0a068 "black_bird", vgid=0x7f5f8ab0a040 "7pu2Bz49SSojNDmv0l9F9qqR79Zlor2w", read_flags=262144, lockd_state=<value optimized out>)
    at metadata/metadata.c:5499
#7  vg_read (cmd=0x7f5f8aac4110, vg_name=0x7f5f8ab0a068 "black_bird", vgid=0x7f5f8ab0a040 "7pu2Bz49SSojNDmv0l9F9qqR79Zlor2w", read_flags=262144, lockd_state=<value optimized out>)
    at metadata/metadata.c:5585
#8  0x00007f5f89243ea7 in _process_pvs_in_vgs (cmd=0x7f5f8aac4110, read_flags=262144, all_vgnameids=0x7ffcacd3a5e0, all_devices=<value optimized out>, arg_devices=<value optimized out>, 
    arg_tags=0x7ffcacd3a620, process_all_pvs=1, process_all_devices=0, handle=0x7f5f8ab09398, process_single_pv=0x7f5f89240210 <_pvscan_single>) at toollib.c:3261
#9  0x00007f5f89249774 in process_each_pv (cmd=0x7f5f8aac4110, argc=<value optimized out>, argv=<value optimized out>, only_this_vgname=0x0, read_flags=262144, handle=0x7f5f8ab09398, 
    process_single_pv=0x7f5f89240210 <_pvscan_single>) at toollib.c:3399
#10 0x00007f5f8923fd0e in pvscan (cmd=0x7f5f8aac4110, argc=0, argv=0x7ffcacd3ab70) at pvscan.c:425
#11 0x00007f5f89233559 in lvm_run_command (cmd=0x7f5f8aac4110, argc=0, argv=0x7ffcacd3ab70) at lvmcmdline.c:1655
#12 0x00007f5f892377e9 in lvm2_main (argc=1, argv=0x7ffcacd3ab68) at lvmcmdline.c:2121
#13 0x00007f5f87f9ed1d in __libc_start_main (main=0x7f5f89254300 <main>, argc=1, ubp_av=0x7ffcacd3ab68, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7ffcacd3ab58) at libc-start.c:226
#14 0x00007f5f8921c269 in _start ()



Version-Release number of selected component (if applicable):
2.6.32-684.el6.x86_64

lvm2-2.02.143-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
lvm2-libs-2.02.143-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
lvm2-cluster-2.02.143-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
udev-147-2.73.el6_8.2    BUILT: Tue Aug 30 08:17:19 CDT 2016
device-mapper-1.02.117-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
device-mapper-libs-1.02.117-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
device-mapper-event-1.02.117-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
device-mapper-event-libs-1.02.117-12.el6    BUILT: Wed Jan 11 09:35:04 CST 2017
device-mapper-persistent-data-0.6.2-0.1.rc7.el6    BUILT: Tue Mar 22 08:58:09 CDT 2016


How reproducible:
Only once
Comment 2 Jan Kurik 2017-12-06 11:49:45 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.