Red Hat Bugzilla – Bug 444415
PV domain with blktap detects error condition during shutdown sequence.
Last modified: 2014-02-02 17:36:35 EST
Description of problem:
When PV domain with blktap device does shutdown, the check of share condition
for blktap device detects mismatch of share information. We don't need the check
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create PV domain with blktap device
2. shutdown PV domain
3. check error message
We saw the following error message,
Apr 15 11:59:49 rx300s3-ken logger: /etc/xen/scripts/blktap: xenstore-read
Apr 15 11:59:49 rx300s3-ken logger: /etc/xen/scripts/blktap:
/etc/xen/scripts/blktap failed; error detected.
There is no error message.
We sent the patch to the community.
hotplug scripts: Fix sharing check for blktap
changeset 17493: 5e3baace443f
Created attachment 303956 [details]
patch fix sharing for blktap
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
This makes sense - it is pointless checking device sharing when unplugging the disk
This bug was actually caused by the original patch for bug 445589. Since we removed that patch this bug does not need to be addressed until we've got a new potential solution for bug 445589.
I have recompiled new RPMs and tested to replicate this BZ with them. I was unable to reproduce it (there were no such messages), could you please download and try this with my RPMs at http://people.redhat.com/minovotn/xen ?
The check for shared devices was removed from blktap script completely, so there's nothing to fix here. A better check is being implemented directly in xend for https://bugzilla.redhat.com/show_bug.cgi?id=345441
I think we could close this bug...
*** This bug has been marked as a duplicate of bug 345441 ***