Bug 442077
Summary: | Using sdaa as a guest device results in corupted device name inside the guest | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jan Mark Holzer <jmh> | ||||
Component: | kernel-xen | Assignee: | Chris Lalancette <clalance> | ||||
Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 5.2 | CC: | gozen, rlerch, sbeal, xen-maint | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Attaching a disk with a specific name (ie. /dev/xvdaa, /dev/xvdab, /dev/xvdbc etc.) to a paravirtualized guest resulted in a corrupted /dev device inside the guest. This update resolves the issue so that attaching disks with these names to a paravirtualized guest creates the proper /dev device inside the guest.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-01-20 21:15:25 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 449772, 454962 | ||||||
Attachments: |
|
Description
Jan Mark Holzer
2008-04-11 16:26:35 UTC
I'll assign this one to myself for now, since I'm going to fix it as part of BZ 442723. I might close it later as a dup, but that's not exactly right so I'll leave it open for the time being. Chris Lalancette Note that this was fixed in upstream xen-unstable changeset 12314; I'll end up backporting that to RHEL-5 as part of BZ 442723. Chris Lalancette 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 release. Created attachment 312448 [details]
Patch to expand the printing of devices (scsi and xvd) in blkfront
in kernel-2.6.18-104.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 in kernel-2.6.18-104.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 This bug has been marked for inclusion in the Red Hat Enterprise Linux 5.3 Release Notes. To aid in the development of relevant and accurate release notes, please fill out the "Release Notes" field above with the following 4 pieces of information: Cause: What actions or circumstances cause this bug to present. Consequence: What happens when the bug presents. Fix: What was done to fix the bug. Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When attaching a disk named sdaa to a paravirtualized guest, the name of the disk would come up as /dev/sd}, instead of the expected /dev/sdaa. This was due to a flaw in the way the paravirtualized frontend named the disk. This is now fixed so that attaching a disk /dev/sdaa shows up as /dev/sdaa in the paravirtualized guest. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1 @@ -When attaching a disk named sdaa to a paravirtualized guest, the name of the disk would come up as /dev/sd}, instead of the expected /dev/sdaa. This was due to a flaw in the way the paravirtualized frontend named the disk. +When a disk named /dev/sdaa disk was attached to the paravirtualized guest, it would be incorrectly renamed to /dev/sd. In this update, this issue has been resolved.- -This is now fixed so that attaching a disk /dev/sdaa shows up as /dev/sdaa in the paravirtualized guest. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When a disk named /dev/sdaa disk was attached to the paravirtualized guest, it would be incorrectly renamed to /dev/sd. In this update, this issue has been resolved.+When a disk named /dev/sdaa (or bigger) was attached to a paravirtualized guest, the name would be corrupted inside the guest. In this update, this issue has been resolved. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When a disk named /dev/sdaa (or bigger) was attached to a paravirtualized guest, the name would be corrupted inside the guest. In this update, this issue has been resolved.+Trying to attach a disk named /dev/sdaa, /dev/sdab, etc. to a paravirtualized guest would result in a corrupted /dev device inside the guest. This update resolves the issue so that attaching /dev/sdaa to a paravirtualized guest creates the proper /dev device inside the guest. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Trying to attach a disk named /dev/sdaa, /dev/sdab, etc. to a paravirtualized guest would result in a corrupted /dev device inside the guest. This update resolves the issue so that attaching /dev/sdaa to a paravirtualized guest creates the proper /dev device inside the guest.+Attaching a disk with a specific name (ie. /dev/sdaa, /dev/sdab, /dev/sdbc etc.) to a paravirtualized guest resulted in a corrupted /dev device inside the guest. This update resolves the issue so that attaching disks with these names to a paravirtualized guest creates the proper /dev device inside the guest. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Attaching a disk with a specific name (ie. /dev/sdaa, /dev/sdab, /dev/sdbc etc.) to a paravirtualized guest resulted in a corrupted /dev device inside the guest. This update resolves the issue so that attaching disks with these names to a paravirtualized guest creates the proper /dev device inside the guest.+Attaching a disk with a specific name (ie. /dev/xvdaa, /dev/xvdab, /dev/xvdbc etc.) to a paravirtualized guest resulted in a corrupted /dev device inside the guest. This update resolves the issue so that attaching disks with these names to a paravirtualized guest creates the proper /dev device inside the guest. 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. http://rhn.redhat.com/errata/RHBA-2009-0118.html |