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 825126 - vgs hungs due to the failing mpath
Summary: vgs hungs due to the failing mpath
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: device-mapper-multipath
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-25 08:04 UTC by Xiaowei Li
Modified: 2015-01-27 00:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-25 10:53:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vgs.log (12.13 KB, application/octet-stream)
2012-05-25 08:19 UTC, Xiaowei Li 		no flags Details
View All

Description Xiaowei Li 2012-05-25 08:04:08 UTC 
Description of problem:
if the multipathed devices are failing, lvm command 'vgs' will hung due to the failed multipathed devices. 

Version-Release number of selected component (if applicable):
2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
lvm2-2.02.87-6.el6.x86_64
device-mapper-multipath-0.4.9-46.el6.x86_64
device-mapper-1.02.66-6.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. configure the iscsi initiator to login the iscsi target 
2. enable multipath and create partition on the iscsi lun
>>lvm.conf, only scan the multpathed devices
    filter = [ "a/mpath/" "r/.*/" ]
>>
# multipath -ll
mpathbq (360060e801047103004f2c4b30000001f) dm-2 HITACHI,DF600F
size=200G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 2:0:0:1 sda 8:0    active ready running
# vgs -o+devices
  VG            #PV #LV #SN Attr   VSize   VFree  Devices                     
  iscsi_vg   1   3   0 wz--n- 199.80g 78.80g /dev/mapper/mpathbqp2(0)    
  iscsi_vg   1   3   0 wz--n- 199.80g 78.80g /dev/mapper/mpathbqp2(5120) 
  iscsi_vg   1   3   0 wz--n- 199.80g 78.80g /dev/mapper/mpathbqp2(30720)

3. sysctl kernel.hung_task_timeout_secs=10 ( hung task can be easily to reproduce ) 
4. ifdown the NIC used by the default iscsi iface
5. execute 'vgs'
  
Actual results:
INFO: task vgs:1781 blocked for more than 10 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message
....

Expected results:
vgs can report some error about the iscsi_vg but can display other VG(if have) and exit gracefully.

Additional info:
Comment 2 Xiaowei Li 2012-05-25 08:19:03 UTC 
Created attachment 586798 [details]
vgs.log
Comment 3 Alasdair Kergon 2012-05-25 08:23:59 UTC 
queue_if_no_path is set, so is this not correct behaviour?

- LVM needs to probe the device.  (But see also lvmetad as future alternative.) 

- You configured your system to say: if this device is unavailable and something tries to access it, wait indefinitely.
Comment 4 Peter Rajnoha 2012-05-25 08:35:02 UTC 
(In reply to comment #0)
> Expected results:
> vgs can report some error about the iscsi_vg but can display other VG(if
> have) and exit gracefully.

I'd say this is just a misconfiguration - if "error" is expected instead, you should consider using the "error if no path" policy that does exactly that ("no_path_retry=fail" setting).

If you encounter this problem while doing a system shutdown, we already track that by bug #800801 (see also original bug #672530 comment #15).
Comment 5 Xiaowei Li 2012-05-25 10:53:52 UTC 
Thanks for the clarification. I got the expected behavior after setting no_path_retry=fail. So close this bug.
Note You need to log in before you can comment on or make changes to this bug.