Bug 11304 - All nodes in /tmp/ida have same Major Number (72).
Summary: All nodes in /tmp/ida have same Major Number (72).
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.2
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
: 11300 11305 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-05-08 19:41 UTC by charles.white
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-07-21 20:48:39 UTC
Embargoed:

Attachments (Terms of Use)

Description charles.white 2000-05-08 19:41:01 UTC 
During a 6.2 install (and 6.1), the nodes created /tmp/ida have the same
Major number.
While c0d0 should be 72, 0.
c1d0 should be 73, 0
c2d0 should be 74, 0...

Because all the nodes in /tmp/ida use 72 all accesses go to controller c0,
not the controller they were intended to.
Comment 1 Jay Turner 2000-05-10 19:31:59 UTC 
*** Bug 11305 has been marked as a duplicate of this bug. ***
Comment 2 Jay Turner 2000-05-10 19:33:59 UTC 
*** Bug 11300 has been marked as a duplicate of this bug. ***
Comment 3 Chris Wood 2000-05-12 10:00:59 UTC 
You may want to take a look at the call of mine that you closed (#11300), as it
has a clue as to where the problem needs to be fixed. My code sample is a hack,
as it only fixes things if you have < three controllers but it may help speed
you towards getting the bug fixed.

Chris
Comment 4 Ken Crandall 2000-06-05 19:25:26 UTC 
The bug is present only at install... 

It's during install do you use the /tmp/ida nodes... 

After install, you use the nodes in /dev/ida which are correct...
Comment 5 Michael Fulbright 2000-06-09 22:24:24 UTC 
This issue is being addressed.
Comment 6 Michael Fulbright 2000-06-22 16:43:54 UTC 
Should be fixed in internal development build.
Comment 7 John Cagle 2000-07-21 20:48:34 UTC 
Compaq Bug Tracking Number 181674
Note You need to log in before you can comment on or make changes to this bug.