Bug 116425
Summary: | Unable to open /dev/sdf | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Brock Organ <borgan> |
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | petrides, riel, shillman |
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: | 2004-03-10 17:09:04 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
Brock Organ
2004-02-20 23:06:29 UTC
I'm a little confused. I'm reading this to say that there are unavailable disks from sdf-sdp, and that fdisk-ing one of those devices causes it to say that it's unable to open it. Why is this a problem? What do you expect/want to be happening? sorry, that is confusing, let me try to be clearer: :) my zfcp map defines 16 scsi disks (sda-sdp) ... so I would expect all 16 disks to be fdisk-able, for example ... 10 of the 16 disks, in fact are available (fdisk-able), but for unknown reasons, 6 of them are not ... this seems to not be present in more recent test trees ... will re-open if I can reproduce it/get more details ... |