Red Hat Bugzilla – Bug 448655
Path down messages are seen during the creation of snapclone/snapshot for a LUN.
Last modified: 2010-01-11 21:42:38 EST
Description of problem:
Path failure messages are seen during the creation of a snapclone/snapshot for
Version-Release number of selected component (if applicable):
This can be reproduce by creating a snapclone/snapshot for a LUN and
constantly monitoring the path status.Paths are seen to be failed for a
fraction of time.
Steps to Reproduce:
1.Create a snapclone/snapshot for a LUN.
2.Check the path status during this process.
Paths are seen to be going down for some time.
Path failures are not expected during this process.
Creation of a snapclone/snapshot for a LUN returns a Unit Attention with a
changed Inquiry data,for TUR. With this, the checker marks the path as down.
But,these conditions can be retried for a fixed number of times to see if it
is corrected and then the paths marked accordingly.
The patch to fix this is availale in the dm-devel mailing list at -
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Is there any update on this bug?
Patch applied. Thanks.
Partners, this bug should be fixed in the latest RHEL 5.3 Snapshot. We believe that you have some interest in its correct functionality, so we're making a friendly request to send us some testing feedback.
If you have a chance to test it, please share with us your findings. If you have successfully VERIFIED the fix, please add PartnerVerified to the Bugzilla keywords, along with a description of the results. Thanks!
~~ Snapshot 6 is out ~~ Partners, please test and let us know if this bug has been fixed. Add PartnerVerified keyword if everything works as expected. For any new issues encountered, CLONE this bug and report the issues in the new bug.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.