this morning (or maybe after a nights rest), revealed the issue from lspv . The lspv hdisk1 this morining also shows the pv state: missing, although lspv shows all the disks online. none of the aix lvm commands are working on the disk (reducevg complains about the open hd2 lv, which is /usr, even if I use -f to force it). syncvg is not running in the background.
This is AIX 6.1 TL7 SP 10 1415 build date. I have had to run odmgets and odmdeletes before on other boxes. a little bit of tedious cleanup isnt all that bad. Unfortunately this is in a remote DC, so I have to rely on another pair of hands to pull the disk.
AND ERRPT shows (finally)
Description
PV NO LONGER RELOCATING NEW BAD BLOCKS
Probable Causes
NON-MEDIA ERROR DURING SW RELOCATION
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
STORAGE DEVICE CABLE
Hello,
how can i see easily the state of a mirrored disk on a AIX 4.3.3.
I try followed command:
lslv -m >lvname> but for me is not enough information.
thanx in advance
fenomen (2 Replies)
I've looked a little but haven't found a solid answer, assuming there is one.
What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Hi ,
I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through
metainit d51 1 1 c0t0d0s2
metainit d52 1 1 c1t0d0s2
In the next step
metainit d50 -m d51
d50: Mirror is setup
next step is
metaattach d50 d52
d50 : submirror d52 is... (7 Replies)
Guys,
In my AIX 6.1 box the rootvg was on hdisk2, I tried to migrated it to hdisk0
Added hisk0 to rootvg , mirrored rootvg and changed bootlist and and sucessfully rebooted from hdisk0
Now I tried to remove the hdisk2 from rootvg so breaked mirror
-bash-3.00# unmirrorvg rootvg hdisk2... (3 Replies)
Dear all.
We have a very big issue on Attach HP EVA to IBM AIX powerpc singlepath.
the configurations on
lscfg -vl fcs2
fcs2 U789C.001.DQD8D74-P1-C2-T1 4Gb FC PCI Express Adapter (df1000fe)
Part Number.................10N7249
Serial... (3 Replies)
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Hello,
aix 5.2, mirrored rootvg on hdisk0 and hdisk1. hdisk0 is dead. I can boot to cd, into sms, into maintenance mode. I can fsck all the various partitions on hdisk1 (the hd4 hd2 hd3, etc...) all is fine. But without the hdisk0 part of the mirror I cannot get the system to boot. ystem hangs on... (6 Replies)
Hello,
I have two hdisk in Power7 machine, the rootvg on hdisk0.
So to make a disk redundancy should make mirror or alt_clone and what is the different.
Appreciate your help
Thanks (1 Reply)
Hi everybody,
I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirroring.
I accidentally created logical volume cpsabcd2lv with external jfs2log loglv00 in the same volume group cpsdata2vg. Then I mirrored LV cpsabcd2lv on the second LUN in VG cpsdata2vg. My journal is unmirrored and... (0 Replies)
Discussion started by: Necronomic
0 Replies
LEARN ABOUT OSF1
volrecover
volrecover(8) System Manager's Manual volrecover(8)NAME
volrecover - Performs volume recovery operations
SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...]
OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started
before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera-
tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available
for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5
parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back-
ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will
be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no
other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list
of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name,
the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume.
State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the
recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume.
Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion
status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim-
its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame
operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated
relative to the given disk group.
Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk
group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu-
ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre-
fix:options can be specified to restrict the set of commands that the -o option should be applied to.
Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity
rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes)
Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies
to mirror resynchronization and RAID5 parity recovery
DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes
residing on the named disks (medianame).
If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group).
If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place.
Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that
involve unrelated disks will run in parallel.
EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command:
# volrecover -b medianame
If you want to monitor the operations, use the command:
# volrecover -v medianame
SEE ALSO volintro(8), volplex(8), volume(8)volrecover(8)