Re: controller numbering
- From: Darren Dunham <ddunham@xxxxxxxxxxxxxxxx>
- Date: Mon, 02 Jul 2007 17:26:39 GMT
Wolfgang <wtrappe@xxxxxxxxx> wrote:
That is what I have done without problems (but also without a lotyou can rename/relink the files in /dev/cfg and
rebuild the depending devices (/dev/dsk /dev/rdsk metadb ...).
I hope not. The numbers should be fixed once assigned based on entries
in /etc/path_to_inst and the links in /dev/cfg.
testing ;-).
But why shouldnt it be possible? A reconfigure reboot should solve in
path_to_inst, shouldnt it?
Depends on what you mean by "solve", but no.
/etc/path_to_inst is there to give a "permanent" assignment to devices.
Rebuilding does not delete past assignments.
Imagine you have 3 storage controllers in the machine: c1, c2, c3.
After a while, you stop using c1 so you remove it from the machine.
When a rebuild occurs, you probably don't want c2 and c3 to suddendly
change to c1, c2.
A Sun engineer told me, the recommended way is to build in the IO-card
in the order you want have the Controller numbers. But that is a time
consuming way and can not change the internal controller.
There's not really a defined user interface to this. In most
situations, the numbering is arbitrary and irrelevant. When a
particular numbering becomes necessary, messing around in
/etc/path_to_inst and friends becomes necessary.
--
Darren Dunham ddunham@xxxxxxxx
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
.
- Follow-Ups:
- Re: controller numbering
- From: Dean
- Re: controller numbering
- From: Andrew Gabriel
- Re: controller numbering
- References:
- Re: controller numbering
- From: Wolfgang
- Re: controller numbering
- Prev by Date: Re: Want a script which consumes memory for testing
- Next by Date: Re: Long process list
- Previous by thread: Re: controller numbering
- Next by thread: Re: controller numbering
- Index(es):
Relevant Pages
|