how to get the dump information(send out the dump to ibmers)?
I just look through some conceptions,attach here
[B]Object Data Manager (ODM) Database[/B]
The ODM database is the place where most of the AIX V3 system
configuration data is kept. The ODM database contains information about all configured physical volumes, volume groups, and logical volumes. This
information mirrors the information found in the VGDA. For example, the
process of importing a VGDA involves copying the VGDA data for the
imported volume group into the ODM. When a volume group is exported, the data held in the ODM about that volume group is removed from the ODM database.
[B]Volume Group Descriptor Area (VGDA)[/B]
The VGDA, located at the beginning of each physical volume, contains
information that describes all the logical volumes and all the physical volumes that belong to the volume group of which that physical volume is a member. The VGDA is updated by almost all the LVM commands. The VGDA makes
each volume group self-describing. An AIX system can read the VGDA on a disk, and from that, the system can determine what physical volumes and logical volumes are part of this volume group.
Each disk contains at least one VGDA. This is important at vary on time. The time stamps in the VGDAs are used to determine which VGDAs correctly reflect the state of the volume group. VGDAs can get out of sync when, for example, a volume group of four disks has one disk failure. The VGDA on that disk cannot be updated while it is not operational. Therefore, you need a way to update this VGDA when the disk comes online, and this is what the vary on process will do.
The VGDA is allocated when the disk is assigned as a physical volume (with the command mkdev). This just reserves a space for the VGDA at the start of the disk. The actual volume group information is placed in the VGDA when the physical volume is assigned to a volume group (using the mkvg or extendvg commands). When a physical volume is removed from the volume group (using the reducevg command), the volume group information is removed from the VGDA.
[B]Volume Group Status Area (VGSA)[/B]
The VGSA contains state information about physical partitions and physical volumes. For example, the VGSA knows if one physical volume in a volume group is unavailable.
Both the Volume Group Descriptor Area and the Volume Group Status Area have beginning and ending time stamps that are very important. These time stamps enable the LVM to identify the most recent copy of the VGDA and the VGSA at vary on time.
The LVM requires that the time stamps for the chosen VGDA be the same as those for the chosen VGSA.
Logical Volume Control Block (LVCB)
The LVCB is located at the start of every logical volume. It contains
information about the logical volume and takes up a few hundred bytes.
The following example shows the use of getlvcb command to display the
information held in the LVCB of logical volume hd6:
[rgjibm1]:[/]>getlvcb -TA hd6
AIX LVCB
intrapolicy = m
copies = 1
interpolicy = m
lvid = 0008889979af7178.2
lvname = hd6
label = None
machine id = 88899A600
number lps = 256
relocatable = y
strict = y
stripe width = 0
stripe size in exponent = 0
type = paging
upperbound = 32
fs =
time created= Thu Feb 20 05:23:41 2003
time modified = Thu Feb 20 05:23:41 2003
[B]Disk Quorum[/B]
Each physical disk in a volume group has at least one VGDA/VGSA. The
number of VGDAs contained on a single disk varies according to the number of disks in the volume group as shown in the following example:
Single PV in a volume group Two VGDAs on one disk.
Two PVs in a volume group Two VGDAs on the first disk, one
VGDA on the second disk.
Three or more PVs in a volume group One VGDA on each disk.
[B]Disk Mirroring[/B]
The [B]mklv[/B] command allows you to select one or two additional copies for each logical volume. Mirroring can also be added to an existing logical volume using the [B]mklvcopy[/B] command. |
