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 843073 - Add the io_timeout to the lockspace api, and make it safe to adjust.
Summary: Add the io_timeout to the lockspace api, and make it safe to adjust.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sanlock
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: Leonid Natapov
URL:
Whiteboard: storage
Depends On:
Blocks: 800588 906027
TreeView+ depends on / blocked
 
Reported: 2012-07-25 13:55 UTC by Leonid Natapov
Modified: 2013-02-21 08:53 UTC (History)
4 users (show)

Fixed In Version: sanlock-2.6-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 08:53:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0530 0 normal SHIPPED_LIVE sanlock bug fix and enhancement update 2013-02-21 02:02:17 UTC

Description Leonid Natapov 2012-07-25 13:55:22 UTC 
The sanlock daemon -o option can be used to set theio timeout, but it's essential that all hosts use the same value, and nothing verifies/enforces this consistency.  We need to add the io_timeout to the lockspace api, and make it safe to adjust.
Comment 2 David Teigland 2012-09-24 15:19:52 UTC 
I think RHEV will want to make use of adjustable i/o timeouts with sanlock, since i/o timeouts are currently adjustable when not using sanlock.
Comment 3 Leonid Natapov 2012-10-04 09:38:04 UTC 
David,what we have to test here ? Give us instructions for QA,please.
Comment 5 David Teigland 2012-10-04 16:51:16 UTC 
Leonid, nothing uses this change yet, although I expect that vdsm will use it.  In the next 6.4 build I'll include Federico's python patch and we'll add a comment here containing the steps to use it.
Comment 6 David Teigland 2012-10-05 15:36:41 UTC 
(This it the test, but a build with command line support for running the test is not yet ready.)

Here are steps to verify that sanlock is correctly accounting for different io timeouts.  The client add_lockspace command should take 2x the prev read_leader io_timeout (plus variable 1-2 seconds).  The add_lockspace is no longer based on the timeout used by the current command (the -o value or 10 if no -o is specified.)

service wdmd start
service sanlock start

dd if=/dev/null of=/root/testfile count=1024 bs=1024
chmod 666 /root/testfile
sanlock direct init -s test:0:/root/testfile:0

sanlock direct read_leader -s test:1:/root/testfile:0 | grep io_timeout
io_timeout 10
# next add_lockspace should take 20 sec

time sanlock client add_lockspace -s test:1:/root/testfile:0
real 0m21.015s

sanlock client rem_lockspace -s test:1:/root/testfile:0
 
sanlock direct read_leader -s test:1:/root/testfile:0 | grep io_timeout
io_timeout 10
# next add_lockspace should take 20 sec

time sanlock client add_lockspace -o 20 -s test:1:/root/testfile:0
real 0m21.020s

sanlock client rem_lockspace -s test:1:/root/testfile:0

sanlock direct read_leader -s test:1:/root/testfile:0 | grep io_timeout
io_timeout 20
# next add_lockspace should take 40 sec

time sanlock client add_lockspace -o 10 -s test:1:/root/testfile:0
real 0m41.009s

sanlock client rem_lockspace -s test:1:/root/testfile:0

sanlock direct read_leader -s test:1:/root/testfile:0 | grep io_timeout
io_timeout 10
# next add_lockspace should take 20 sec

time sanlock client add_lockspace -o 5 -s test:1:/root/testfile:0
real 0m21.005s

sanlock client rem_lockspace -s test:1:/root/testfile:0

sanlock direct read_leader -s test:1:/root/testfile:0 | grep io_timeout
io_timeout 5
# next add_lockspace should take 10 sec

time sanlock client add_lockspace -o 20 -s test:1:/root/testfile:0
real 0m11.005s
Comment 7 David Teigland 2012-10-09 16:28:56 UTC 
This can now be tested with build sanlock-2.6-1
Comment 8 Leonid Natapov 2013-01-20 15:53:22 UTC 
sanlock-2.6-2.el6.x86_64
Comment 10 errata-xmlrpc 2013-02-21 08:53:14 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, 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-2013-0530.html
Note You need to log in before you can comment on or make changes to this bug.