Re: Replace a rootvg hard disk with different capacity
From: DT (odn_at_sinaman.com)
Date: 08/28/03
- Next message: VinceM: "Re: Access to AS/400 data"
- Previous message: Peter Keller: "Re: Model and CPU"
- In reply to: Jano: "Re: Replace a rootvg hard disk with different capacity"
- Next in thread: Steve Nottingham: "Re: Replace a rootvg hard disk with different capacity"
- Reply: Steve Nottingham: "Re: Replace a rootvg hard disk with different capacity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 29 Aug 2003 02:02:24 +0800
Hi Jano,
Thanks you for your reply, I will test it with testing machine before going
to live.
- DT
"Jano" <bradounet1@caramail.com> wrote in message
news:3F4E1C94.5030007@caramail.com...
> Migrating rootvg to Another Disk Drive
> This document discusses the procedures specific to the rootvg volume
> group on how to migrate the contents on one physical volume to another
> physical volume in the same volume group.
>
> This document applies to all levels of AIX Versions 4 and 5.
>
> WARNING: Please do not use this document if the system is a /usr client,
> diskless client, or dataless client.
>
> General steps for migrating contents of a physical volume
> Recommended fixes
> Related documentation
>
>
>
> --------------------------------------------------------------------------
------
>
> General steps for migrating contents of a physical volume
> NOTE: Before performing these instructions, please ensure that all fixes
> listed at the end of this document are installed for your system's level
> of AIX.
> The command to move data from one physical volume to another physical
> volume within the same volume group is called migratepv. The usage
> parameters for this command are as follows:
>
> migratepv [-i] [-l LVname] <SourcePV> <DestinationPV...>
>
> More than one destination physical volume can be specified.
> The first steps are to identify what disk you want to migrate and what
> disks to which you want to migrate it. First, you can only migrate to
> disks that are already in the rootvg volume group. To get a list of
> disks that are already in the rootvg volume group, run the command lsvg
> -p rootvg.
>
> Example:
>
> # lsvg -p rootvg
> rootvg:
> PV_NAME PV STATE TOTAL PPs FREE PPs FREE
DISTRIBUTION
> hdisk0 active 515 116
57..00..00..00..59
> hdisk1 active 515 515
00..00..00..00..00
>
> Now, determine the space that is currently being used on the disk you
> wish to migrate. This will be the TOTAL PPs value minus the FREE PPs
> value for the desired disk. In the preceding example, choose hdisk0,
> which is using (515 - 116) PPs or 399 physical partitions.
> Then find a disk or disks that have the available space. In this case,
> hdisk1 has 515 free physical partitions, which is more than the required
> space of 399 physical paritions and will fulfill our needs.
>
> The only situation that is specific to rootvg is if the desired disk
> contains the boot image. Generally, this will be the logical volume
> called hd5 and will have a type of boot, as shown from a partial list of
> lsvg -l rootvg:
>
> LV NAME TYPE LPs PPs PVs LV STATE MOUNT
> POINT
> hd5 boot 1 1 1 closed/syncd N/A
>
> To determine if the boot image is on the disk you wish to migrate, run
> the lslv -l <bootlvname> command.
> Example:
>
> # lslv -l hd5
> hd5:N/A
> PV COPIES IN BAND DISTRIBUTION
> hdisk0 001:000:000 100% 001:000:000:000:000
>
> In this case, the boot image resides on the disk we wish to migrate. The
> boot image will need to be moved first. Do so with the command migratepv
> -l <bootimage name> <source disk> <destination disk>.
> Example:
>
> #migratepv -l hd5 hdisk0 hdisk1
>
> NOTE: The destination disk must be supported as a boot disk. Run the
> command bootinfo -B <hdisk#> to determine if the disk is supported as a
> boot disk. If the command returns 1, then it is supported as a boot
> disk. AIX 4.2 and later will present a warning from the migratepv
> command if the destination disk is not bootable.
> After the boot image has been moved, the boot record on the original
> disk should be cleared to prevent possible problems if the machine
> accidentally attempted to boot from this disk. Use the mkboot -c - d
> /dev/<hdisk#> command on the source disk to clear the boot record.
>
> Example:
>
> #mkboot -c -d /dev/hdisk0
>
> Afterward, update the boot image on the new destination disk. Run
> bosboot -a -d /dev/<hdisk#> for the destination disk to rebuild the boot
> image and generate a new boot record on the source disk.
> Example:
>
> #bosboot -a -d /dev/hdisk1
>
> Now, update the bootlist so that the system will know where to find the
> new hd5.
>
> Example:
>
> #bootlist -m normal hdisk1
>
> At this point, you can migrate the rest of the contents of the source
> physical volume to the destination disk or disks.
>
> Example:
>
> #migratepv hdisk0 hdisk1
>
> Once this command has completed, the migration will be complete.
> --------------------------------------------------------------------------
------
>
> Recommended fixes
> APAR DESCRIPTION AIX LEVEL
> IX61186 BOSBOOT DOESN'T WORK ON A BLV MIRROR V4.1
> IX74042 MIGRATEPV NEEDS TO MIGRATE MIRRORS V4.1
> OFF OF DEAD DISKS
> IX76351 BOSBOOT DOESN'T VALIDATE DEVICE V4.1
> CORRECTLY
> IX62417 BOSBOOT DOESN'T WORK ON A BLV MIRROR V4.2
> IX68140 MIGRATEPV, MIRRORVG, AND UNMIRRORVG V4.2
> NEED TO HANDLE BLV CASES
> IX74905 BOOT RAM FILESYSTEM IS TOO SMALL V4.2
> IX74041 MIGRATEPV NEEDS TO MIGRATE MIRRORS V4.2
> OFF OF DEAD DISKS
> IX66626 BOSBOOT DOESN'T VALIDATE DEVICE V4.2
> CORRECTLY
> IX73591 MIGRATEPV NEEDS TO MIGRATE MIRRORS V4.3
> OFF OF DEAD DISKS
> IY18181 MIGRATEPV FAILING WITH MULTIPLE V4.3
> DESTINATION PVS
> IY12157 MIGRATEPV FAILS W/O TARGET PVS V4.3
> IX68698 ALLOCP: MIGRATEPV FAILS FOR MIRRORED V4.3
> LVS
> IY28528 MIGRATEPV IGNORES STRICTNESS POLICY V4.3
> IY27901 MIGRATEPV/REPLACEPV FAILURE V4.3
> IY18861 MIGRATEPV FAILING WITH MULTIPLE V4.3
> DESTINATION PVS
>
>
> --------------------------------------------------------------------------
------
>
> Related documentation
> For more in-depth coverage of this subject, the following IBM
> publications are recommended:
>
> AIX Version 4.3 System Management Guide: Operating System and Devices
> (SC23-2525)
> AIX Version 5.1 System Management Guide: Operating System and Devices
> AIX Version 4.3 Commands Reference (references for lsvg, lslv,
> migratepv, and mkboot)
> AIX Version 5.1 Commands Reference
>
>
> DT wrote:
> > Platform: 44P
> > OS: AIX 4.3.3 with ML10
> > Hard disk: one 9.1 GB hard disk only with rootvg
> >
> > I plan to mirror the current rootvg to the new 18.2GB, then remove the
old
> > one while booting to the new hdisk.
> > What is the correct steps to execute and command that I want to used.
> >
> > Any advise are welcome.
> > Thanks.
> >
> > - DT
> >
> >
> >
>
- Next message: VinceM: "Re: Access to AS/400 data"
- Previous message: Peter Keller: "Re: Model and CPU"
- In reply to: Jano: "Re: Replace a rootvg hard disk with different capacity"
- Next in thread: Steve Nottingham: "Re: Replace a rootvg hard disk with different capacity"
- Reply: Steve Nottingham: "Re: Replace a rootvg hard disk with different capacity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
