From: Hunter, Mark (Mark.Hunter@ANHEUSER-BUSCH.COM)
Date: Wed Jul 30 2003 - 09:57:34 EDT
Hmmm...
When we did it, same basic procedure, the mirrorvg bombed on us. Must be some
other twist on the specific issue. I will check with my cohort to see exactly
what else he did.
We also have successfully done this before. IBM admits its a problem but will
not fix it for aix 4.3.3 because it is going away.
-----Original Message-----
From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
Sent: Tuesday, July 29, 2003 6:22 PM
To: aix-l@Princeton.EDU
Subject: Re: [Q] rootvg mirror question?
Hi Mark,
I'm not sure why I'm being so stubborn on this one, but I couldn't run 24x7
without this capability. It's saved me a reboot several times. What good are
hot swap system drives otherwise? I've always thought this function to be
fundamental.
I just hot swapped a replacement drive in rootvg, did a mirrorvg and a
bosboot and bootlist without a reboot.
# lspv |grep " rootvg"
hdisk3 0070270349f5dbb0 rootvg
hdisk9 00702703a48a0e73 rootvg
# unmirrorvg rootvg hdisk9
0516-1246 rmlvcopy: If hd5 is the boot logical volume, please run 'chpv -c
<diskname>'
as root user to clear the boot record and avoid a potential boot
off an old boot image that may reside on the disk from which this
logical volume is moved/removed.
0516-1144 unmirrorvg: rootvg successfully unmirrored, user should perform
bosboot of system to reinitialize boot records. Then, user must
modify
bootlist to just include: hdisk3.
# reducevg rootvg hdisk9
# lspv |grep " rootvg"
hdisk3 0070270349f5dbb0 rootvg
# rmdev -dl hdisk9
hdisk9 deleted
*** Physically replaced hdisk9 with a spare disk
# cfgmgr
# lspv |grep hdisk9
hdisk9 none None
# bootinfo -B hdisk9
1
# extendvg rootvg hdisk9
0516-1254 extendvg: Changing the PVID in the ODM.
# mirrorvg -S rootvg hdisk9
0516-1124 mirrorvg: Quorum requirement turned off, reboot system for this
to take effect for rootvg.
0516-1126 mirrorvg: rootvg successfully mirrored, user should perform
bosboot of system to initialize boot records. Then, user must
modify
bootlist to include: hdisk3 hdisk9.
# bosboot -ad /dev/hdisk9
bosboot: Boot image is 12301 512 byte blocks.
# bootlist -m normal hdisk3 hdisk9 cd0
Did I miss anything?
I think this works because the list of bootable drives that is created at
boot time does not change when you rmdev, replace the disk and run cfgmgr.
Kevin
-----Original Message-----
From: Hunter, Mark [mailto:Mark.Hunter@ANHEUSER-BUSCH.COM]
Sent: Tuesday, July 29, 2003 5:36 AM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] [Q] rootvg mirror question?
Because when you mirrorvg with the new hdisk1, you will get an error - disk
not
bootable and it will fail.
Mark
-----Original Message-----
From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
Sent: Monday, July 28, 2003 4:05 PM
To: aix-l@Princeton.EDU
Subject: Re: [Q] rootvg mirror question?
Mark,
Let's say I boot my system and I now have hdisk0 and hdisk1 and I mirror
rootvg using mirrorvg and I bosboot and add hdisk0 and hdisk1 to the
bootlist.
Now hdisk1 fails. So I unmirrorvg, reducevg and rmdev hdisk1.
Now I swap out hdisk1 for a new one and run cfgmgr and hdisk1 is back.
Now I extendvg, mirrorvg, bosboot (all with hdisk1) and I'm good to go. My
bootlist is still good too without doing a thing, but I could re-add it.
What's not to work?
By the way, why do you reboot before applying patches?
Kevin
-----Original Message-----
From: Hunter, Mark [mailto:Mark.Hunter@ANHEUSER-BUSCH.COM]
Sent: Monday, July 28, 2003 11:53 AM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] [Q] rootvg mirror question?
Well, like all things, yes and no.
If you use mirrorvg, you will get an error about not bootable because the
new
hdisk1 is not listed as bootable. You can mirror by hand (mklvcopy) and
everything should be ok. However, until you reboot, you can not change the
bootlist to include the new disk. Since your old hdisk1 would have been in
the
bootlist, you will reboot fine. If you need to update the OS though, I
don't
think you can do the bosboot because bootinfo -B hdiskX will fail. We only
reboot once or so a year, so most boots == OS patching. Which will require
us
to reboot first, then patch, then reboot.
-----Original Message-----
From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
Sent: Monday, July 28, 2003 1:23 PM
To: aix-l@Princeton.EDU
Subject: Re: [Q] rootvg mirror question?
Simon,
I must be missing the point because I'm sure I've done this before, i.e.,
swap out hdisk0 or hdisk1 and mirrorvg without rebooting.
If you're already setup and have mirrored hdisk0 and hdisk1, and you have a
failure in hdisk1, you should be able to swap and remirror, since hdisk1 is
already marked bootable.
What am I missing? The original post mentioned the above scenario didn't it?
I could see the problem if you added and new disk and it created a new hdisk
that wasn't there at previous boot.
Kevin Adams
PacifiCare Behavioral Health
Principal Systems Analyst
AIX Certified Advanced Technical Expert
-----Original Message-----
From: Green, Simon [mailto:Simon.Green@EU.ALTRIA.COM]
Sent: Monday, July 28, 2003 3:18 AM
To: aix-l@Princeton.EDU
Subject: Re: [aix-l] [Q] rootvg mirror question?
Couldn't you still re-mirror rootvg? You just wouldn't be able to make the
replacement disk bootable at first. That would still give you some
protection until a re-boot could be arranged.
Not an ideal situation, however, and one I would hope IBM will address in
the near future, since they claim to be placing so much importance on
availability.
Simon Green
Altria ITSC Europe Ltd
AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
N.B. Unsolicited email from vendors will not be appreciated.
> -----Original Message-----
> From: Hunter, Mark [mailto:Mark.Hunter@ANHEUSER-BUSCH.COM]
> Sent: 23 July 2003 22:09
> To: aix-l@Princeton.EDU
> Subject: Re: [Q] rootvg mirror question?
>
>
> Well, almost.
> You can not replace and remirror rootvg. The list of
> bootable drives is
> configured at boot time and can not be changed without a
> reboot. The new disk
> will not be listed until a reboot. You can replace any non
> rootvg on the fly
> and be ok.
This electronic message transmission, including any attachments, contains
information from PacifiCare Health Systems Inc. which may be confidential or
privileged. The information is intended to be for the use of the individual
or
entity named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this information
is
prohibited.
If you have received this electronic transmission in error, please notify
the
sender immediately by a "reply to sender only" message and destroy all
electronic and hard copies of the communication, including attachments.
This electronic message transmission, including any attachments, contains
information from PacifiCare Health Systems Inc. which may be confidential or
privileged. The information is intended to be for the use of the individual
or
entity named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this information
is
prohibited.
If you have received this electronic transmission in error, please notify
the
sender immediately by a "reply to sender only" message and destroy all
electronic and hard copies of the communication, including attachments.
This electronic message transmission, including any attachments, contains
information from PacifiCare Health Systems Inc. which may be confidential or
privileged. The information is intended to be for the use of the individual or
entity named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this information is
prohibited.
If you have received this electronic transmission in error, please notify the
sender immediately by a "reply to sender only" message and destroy all
electronic and hard copies of the communication, including attachments.
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:04 EDT