Bug 245681
| Summary: | I/O errors from guest FS running from LVM+raid volume | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | kennyt <kennyt> | ||||||||
| Component: | kernel-xen | Assignee: | Eduardo Habkost <ehabkost> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 7 | CC: | sean, triage, xen-maint | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i386 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-06-17 01:42:48 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
kennyt
2007-06-26 02:30:39 UTC
Created attachment 157846 [details]
the error desc. file anaconda offered to send to a remote server on failure
The guest kernel throwing I/O errors wrt to the virtual disk. <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 <4>end_request: I/O error, dev xvda, sector 5124735 I/O errors in the virtual disk are generally propagated through from the host, so I'm thinking something is wrong on your host storage. Can you provide the /var/log/messages & /var/log/xen/xend.log from the host, immediately after the failure. Also, can you re-run virt-install, adding the --debug command line argument & attach the output it generates. Here are some of the dom0 errors that go with those (these are just the ones from the last window of dmesg): raid0_make_request bug: can't convert block across chunks or bigger than 64k 83907455 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83904633 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83904765 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83904891 3 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905023 3 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905147 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905279 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905405 3 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905529 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905661 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905785 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83905919 3 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83887613 4 raid0_make_request bug: can't convert block across chunks or bigger than 64k 83895807 2 Created attachment 157848 [details]
output from virt-install + --debug
Created attachment 157849 [details]
anaconda dump
The exported logical volume is in a volume group that resides on a single raid0 array. Nothing on the other logical volumes causes any error. The combination of Xen blkback + LVM + raid seems to be causing I/O errors in your dom0. These get propagated up into the guest & thus anaconda crashes & burns. So re-assigning as this is a kernel bug really... This seems to be the same problem reported on bug #223947. Reassigning bug to me. change QA contact This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |