Bug 38949
Summary: | Can't mount CDROM with mount-2.10r-0.6.x under 6.2 alpha | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | jnam1 <jnam1> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | CC: | bero |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-05-03 15:27:09 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
jnam1
2001-05-03 13:54:52 UTC
This looks like a broken drive or a broken medium to me. Definitely not a mount bug, assigning to kernel because if it's a bug (which I doubt), it's a kernel bug. Hi, I am also running two redhat-6.2 x86 boxes here. They have all the recent updates from updates.redhat.com and both machines are identical in terms of rpms loaded. They are now running mount-2.10r-0.6.x.i386 and the same cdrom which you were suspicious of its being broken reads simply perfect on both x86 boxes. Yes, this could be alpha specific kernel issue. But RedHat still should provide a working 'mount' binary consistent with the following rpms anyway by updating whatever found to be broken among them. . kernel-2.2.19-6.2.1.alpha . util-linux-2.10r-0.6.x.alpha (maybe irrelevant but not yet available) . losetup-2.10r-0.6.x.alpha (found to be built from util-linux-2.10r) . mount-2.10r-0.6.x.alpha (found to be built also from util-linux-2.10r) While trying to downgrade mount-2.10r, rpm message says I cannot go back to the previous 2.2.16-3 because it requires kernel >= 2.2.19. regards, Joonwoo Since fixed So, what has been fixed ? Do you think this is not because of the kernel but because of the hardware issue itself ? Joonwoo |