Re: Re-creating system dump logical volume after replacing disk
From: Patrick B. O'Brien (pobrien_at_DOIT.NV.GOV)
Date: 08/05/05
- Previous message: Naylor, Jim: "Re: Re-creating system dump logical volume after replacing disk"
- Maybe in reply to: Naylor, Jim: "Re-creating system dump logical volume after replacing disk"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 5 Aug 2005 07:53:16 -0700 To: aix-l@Princeton.EDU
syncvg -p hdisk1, ????
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Naylor, Jim
Sent: Friday, August 05, 2005 7:46 AM
To: aix-l@Princeton.EDU
Subject: Re: Re-creating system dump logical volume after replacing disk
Thanks Juan but that didn't work. I got this message.
str728> synclvodm -v -P rootvg hd7
synclvodm: Physical volume data updated.
0516-532 synclvodm: Logical volume hd7 not found in volume group rootvg.
Thanks,
Jim Naylor
Unix/Storage Systems Administrator
Schnuck Markets, Inc.
* Direct (314) 994-4784
))( Cell (314) 691-0186
Fax (314) 994-4684
* E-Mail jnaylor@schnucks.com
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
Juan Camilo Yanquen
Sent: Friday, August 05, 2005 9:25 AM
To: aix-l@Princeton.EDU
Subject: Re: Re-creating system dump logical volume after replacing disk
You may try:
synclvodm -v -P rootvg hd7
ATT:
JCY.
---- Original Message ----
From: Naylor, Jim
Date: Fri 8/5/05 9:22
To: aix-l@Princeton.EDU
Subject: Re-creating system dump logical volume after replacing
disk
Hello All,
I have an 43P-150 running AIX 4.3.3 with two internal disk which are
mirrored
(rootvg). The primary disk (hisk0) went bad. This is the procedure I
normally use
when replacing a mirrored rootvg disk.
1- unmirror the rootvg (in this case drop the mirror from hdisk0
2- Remove the primary dump device from the bad drive using the following
procedure.
The secondary dumpdevice is on hdisk1 (/dev/hd72):
# sysdumpdev
# sysdumpdev -P -p /dev/sysdumpnull
# sysdumpdev -l
# sysdumpdev -K
# bosboot -ad /dev/hdisk1
# lslv -l hd7
# rmlv hd7
# lslv -l hd7
3- Reduce volume group of hdisk0
4- Shutdown the system and replace the bad disk
5- Re-boot the system and do a lspv to see if the new drive is
available
6- format/verify the new disk
7- extend the volume group (rootvg) to include hdisk0
8- Mirror rootvg
9- Recreate the primary dump device hd7 using the following procedure:
# mklv -y hd7 sysdump -ae rootvg 6 hdisk0
^
number of
logical partitions
from lsvg -l rootvg (LPs)
# sysdumpdev -P -p /dev/hd7
# sysdumpdev -K
# bosboot -ad hdisk0
# bosboot -ad hdisk1
I have done this many time without any problem but for some reason I am
having
problems recreating the primary dump device. When I ececute the mklv
command I get
the following error:
str728> mklv -y hd7 -t sysdump -ae rootvg 6 hdisk0
0516-360 getlvname: The device name is already used; choose a
different name.
0516-822 mklv: Unable to create logical volume.
I did the following command and this is what I get:
str728> lslv hd7
LOGICAL VOLUME: hd7 VOLUME
GROUP: rootvg
LV IDENTIFIER: 0000e9cbed2fc5e4.16 PERMISSION:
?
VG STATE: active/complete
LV STATE:
?
TYPE: sysdump
WRITE
VERIFY: ?
MAX LPs: ?
PP
SIZE: ?
COPIES: ?
SCHED POLICY: ?
LPs: ?
PPs: ?
STALE PPs: ?
BB
POLICY: ?
INTER-POLICY: minimum
RELOCATABLE:
yes
INTRA-POLICY: middle
UPPER BOUND:
32
MOUNT POINT: N/A
LABEL:
None
MIRROR WRITE CONSISTENCY: ?
EACH LP COPY ON A SEPARATE PV ?: yes
I did a ls -l /dev/hd5 and it did not exist. I tried creating hd5 using
mkod but did
not help. Any idea how I can clean this issue.
Thanks,
Jim Naylor
Unix/Storage Systems Administrator
Schnuck Markets, Inc.
* Direct (314) 994-4784
))( Cell (314) 691-0186
Fax (314) 994-4684
* E-Mail jnaylor@schnucks.com
- Previous message: Naylor, Jim: "Re: Re-creating system dump logical volume after replacing disk"
- Maybe in reply to: Naylor, Jim: "Re-creating system dump logical volume after replacing disk"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
