View Single Post

   
  #5 (permalink)  
Old 03-28-2008, 05:29 AM
jthomp1515@yahoo.com
 
Posts: n/a
Default Re: Wrong numbering of the internal disk for rootvg

On Mar 26, 7:22 am, "F. Michael Orr" <michael_or...@yahoo.com> wrote:
> On Wed, 26 Mar 2008 02:48:59 -0700, Mark Taylor wrote:
> > rcee, thats great and really illutrates a good point with AIX .. as
> > cfgmgr walks the bus configuring devices .. the first disk it comes
> > across will be hdisk0, the next hdisk1 etc .. . have you seen the scsi
> > location numbers ?? 05-08-02 first, then 06-08-00 and then 07-08-02 ..
> > so, like Hajo said, disconnect the fibres and install again ..or
> > ..disconnect the fibres, blow away the FC disks, drop the 2nd rootvg our
> > of rootvg and blow away, then cfgmgr, mirror, drop the second etc... you
> > can change the device names in the odm also is a quicker and **not so
> > safe way**

>
> > Rgds
> > Mark Taylor

>
> Why do you care what hdisk numbers get assigned to rootvg? It is mildly
> annoying that they change, but it doesn't affect the system in any
> meaningful way, assuming that the bootlist command still shows these new
> disks as the boot disks. The above seems to me to be a lot of work and
> potential for harm for a change that has no real benefits. A cost-risk
> analysis says this is not worth it, IMO.



check out lsdev -p and cfgmgr -l

seems like your fibre and you internals would be on different scsi
devices:
here's an example:

lsdev -p scsi0
hdisk0 Available 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 1S-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive
hdisk3 Available 1S-08-00-11,0 16 Bit LVD SCSI Disk Drive
ses0 Available 1S-08-00-15,0 SCSI Enclosure Services Device

assuming you current fibre hdisk0, hdisk1 are on something OTHER than
scsi0 you can :

unmirror rootvg , reduce out hdisk35

rmdev hdisk0 and hdisk35

cfgmgr -l scsi0

that will run ONLY against devices on scsi0-- will prolly leave fibre
alone.

re-mirror rootvg , drop the other hdisk wash rinse repeat, etc

no guarantees expressed or implied. It looks like hdisk0 is just a
LUNZ so it doesn't matter , hdisk1 looks to be a real disk so you'll
need some kind of outage to do this anyway.



Reply With Quote