Bug 106602
Summary: | LTC4825-dasd_diag device not recognized | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Duane Beyer <dbeyer> |
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | billgo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | s390 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-10-16 19:01:55 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: |
Description
Duane Beyer
2003-10-08 19:55:45 UTC
Forget it, seriously. For some reason Martin Schwindefsky thinks it is unsafe to enable disk diagnostics on s390x. It is the same way in 2.6. So, one part of IBM thinks it cannot be done, another part of IBM thinks it should be done. I don't want to meddle into it. NOTABUG. *** This bug has been marked as a duplicate of 105023 *** Hi, I've read the duplicate record (105023) and that discusses s390x (64bit) but says it should work on s390 (31bit). My attempts detailed above were made on a s390 (31bit) image. This disk can be used as vdisk space for increased performance. Thanks. I'm on vacation until 10/23, so I am reopening and reassigning to keep this on radar. No need to keep it open Pete. The device was not getting properly attached to the image. Sorry, our error. Works fine on 31bit. Please close. |