01-15-2019
Quote:
Originally Posted by
mrmurdock
(reducevg complains about the open hd2 lv, which is /usr, even if I use -f to force it).
That was to be expected. I repeat:
Quote:
Do an unmirrorvg to completely make the disk empty and a reducevg to get it out of the VG.
You cannot use a
reducevg on a disk which has not been emptied before. Since you have still a LV occupying space on the PV (even if it is only a mirror) you cannot remove the disk from the VG. You either have to remove the mirror on this disk first or move it to another PV.
If this is not due to a broken cable or controller (that would explain the "missing" status) the error message suggests that the disk was in its last throes anyway: when a disk is formatted (when included in a VG) a certain number of blocks is set aside to compensate for blocks going bad. They are used up over time. Once they are depleted (or nearly depleted) you usually see a series of TEMP hdisk errors (IIRC "hdisk error 3", usually stretched out over some days or weeks) before finally a PERM (IIRC "hdisk error 4") one in the
errpt.
I hope this helps.
bakunin
Last edited by bakunin; 01-15-2019 at 05:46 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: fenomen
2 Replies
2. Solaris
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)
Discussion started by: Lespaul20
3 Replies
3. Solaris
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)
Discussion started by: vr_mari
7 Replies
4. AIX
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)
Discussion started by: kkeng808
3 Replies
5. AIX
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)
Discussion started by: Juri_al
3 Replies
6. AIX
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)
Discussion started by: filosophizer
9 Replies
7. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
8. AIX
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)
Discussion started by: sshapiro
6 Replies
9. AIX
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)
Discussion started by: moudmm
1 Replies
10. UNIX for Beginners Questions & Answers
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
volmirror
volmirror(8) System Manager's Manual volmirror(8)
NAME
volmirror - Mirrors volumes on a disk or control default mirroring
SYNOPSIS
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] medianame [new_medianame...]
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] -a [new_medianame...]
/usr/sbin/volmirror [-g diskgroup] [-d yes|no]
/usr/sbin/volmirror [-g diskgroup] -D
OPTIONS
The volmirror command supports the following options: Limits operation of the command to the given disk group, as specified by disk group
ID or disk group name. The medianame operands will be evaluated relative to the given disk group. If no disk group is supplied to the
volmirror command, rootdg is presumed. Changes the default for subsequent volume creation, depending on the option argument. If the option
argument is yes, all subsequent volumes created using the volassist command will automatically be created as mirrored volumes. If the
option argument supplied is no, mirroring will be turned off for future volumes by default. Displays current default status for mirroring.
Mirrors all existing volumes for the specified disk group.
DESCRIPTION
The volmirror command provides a mechanism to mirror all the contents of a specified disk, to mirror all currently unmirrored volumes in
the specified disk group, or to change or display the current defaults for mirroring. All volumes that have only a single plex (mirror
copy), will be mirrored by adding an additional plex.
Volumes containing subdisks that reside on more than one disk will not be mirrored by volmirror.
The volmirror command is generally called from the voldiskadm menus. It is not an interactive command and once called, will continue until
completion of the operation or until a failure is detected.
Note
Due to the nature of generating mirror copies of volumes, this command may take a considerable time to complete.
In the first listed form of the command, the disk media name is supplied on the command line to volmirror. That name is taken to be the
only disk from which volumes should be mirrored. In the case of mirroring volumes from a specified disk, only simple single-subdisk volumes
are mirrored.
In the first and second listed forms of the command, the new_medianame ... parameter identifies a new disk media name (or set of names).
The mirroring operation being performed will use these names as targets on which to allocate the mirrors. An error will result if the same
disk is specified for both the source and target disk and if no other viable targets are supplied.
EXAMPLES
The following are examples of the use of the volmirror command. The following command mirrors the contents of the disk named disk01 to any
available space on any available disk. Subsequent calls to volassist will cause created volumes to be mirrored by default. volmirror -d
yes disk01 The following command displays the current status of default mirroring. It prints the string yes if mirroring is currently
enabled or no, if not. volmirror -D The following command mirrors any volumes on disk02 onto disk03. volmirror disk02 disk03
FILES
The defaults file for volassist parameters.
SEE ALSO
volintro(8), volassist(8), volrootmir(8)
volmirror(8)