Sponsored Content
Operating Systems AIX Trouble removing Physical Disk from Volume Group Post 303026981 by rbatte1 on Thursday 6th of December 2018 08:29:35 AM
Old 12-06-2018
First, before anything else, backup your data and make sure it is recoverable in a usable way.
Two tested copies at least.


Looking at this part ....
Code:
#  lspv -l hdisk1
hdisk1:
LV NAME               LPs     PPs     DISTRIBUTION          MOUNT POINT
clodba                719     719     40..223..222..223..11 N/A
# lspv -l hdisk2
hdisk2:
LV NAME               LPs     PPs     DISTRIBUTION          MOUNT POINT
clodba                720     721     00..144..223..223..131 N/A

.... suggests the logical volume is mirrored (as suggested) but you must have (at least) one LP that map to PPs that are both on hdisk2. That's a bit of a problem to the point that it's probably not worth mirroring. Lose hdisk2 and you lose logical volume integrity, the filesystem and data. It may be recoverable as far as the filesystem goes, but the data loss is unpredictable.

You may be able to turn on relocation with a chlv or a chvg -b ....command and force the re-sync. What does the full output of lslv -m clodba give you? Sadly it will be quite long given the number of LPs. You will probably see that copy 1 is entirely on hdisk1 except for one PP. You might manage to force the removal of the PPs from hdisk1 with rmlvcopy clodba 1 hdisk1 and if that works, you will have hdisk1 empty (check lspv -l hdisk1) and hdisk2 should be reduced to just 720 PPs in use.

For the future I would consider setting the volume group mirror pool strictness (is that the -M flag?) to force PPs for each LP to be on separate PVs and even to keep LV copies from being mixed across volumes. Personally, I'm more anorak than that and force the creation/extention to use the PPs I set, but that's just me.


Does that help?
Robin
This User Gave Thanks to rbatte1 For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

Having problems with removing a volume group..

Dear all, I would be very grateful if you could help me with removing the volume group.. The case is that, I was trying to create a volume group with 4 disk eligible, but the system has hang .. Maybe because the disks that I was trying to include into the new volume group were of too large size... (5 Replies)
Discussion started by: dilshik
5 Replies

2. UNIX for Dummies Questions & Answers

physical volume and physical disk.

Hello, I need explanations about physical disks and physical volumes. What is the difference between these 2 things? In fact, i am trying to understand what the AIX lspv2command does. Thank you in advance. (2 Replies)
Discussion started by: VeroL
2 Replies

3. AIX

Volume Group disk dead

AIX 4.3.3, 3 drive mirrored stripe. I can't replace the failed drive for at least a week and the VG is down hard. Any way to recover the VG using the mirror copy? Something like this: break the mirror redefine the VG with the mirrored hdisks replace the drive remirror using the original VG... (1 Reply)
Discussion started by: mlcboy01
1 Replies

4. HP-UX

Unmount and remove all Logical vol.Volume group and physical disk

Hi, Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby. (3 Replies)
Discussion started by: joeli
3 Replies

5. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

6. Shell Programming and Scripting

Need to create an for loop for adding an disk in veritas volume group.

Hi Experts I need an script to add an disk in to the veritas volume manager disk group. For example: # cd /tmp # view disk c6t5d2 c6t2d1 c6t3d7 c6t11d2 c7t11d2 c6t11d6 Normally we add the disk like this: # vxdg -g freedg freedisk01=c6t5d2 # vxdg -g freedg freedisk02=c6t2d1 #... (3 Replies)
Discussion started by: indrajit_preet
3 Replies

7. Red Hat

Removing LVM Volume Group that doesn't exist anymore

Our SAN administrator decided to unpresent then destroy LUN's we were actively using as a volume group (all PV's in said volume group). Now every time I do a pvscan or whatever it complains about I/O errors trying to access those PV's. How do I get it to forget the VG existed completely? vgreduce... (7 Replies)
Discussion started by: thmnetwork
7 Replies

8. Linux

Logical Volume to physical disk mapping

When installing Linux, I choose some default setting to use all the disk space. My server has a single internal 250Gb SCSI disk. By default the install appears to have created 3 logical volumes lv_root, lv_home and lv_swap. fdisk -l shows the following lab3.nms:/dev>fdisk -l Disk... (2 Replies)
Discussion started by: jimthompson
2 Replies

9. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies

10. Solaris

Exporting physical disk to ldom or ZFS volume

Generally, this is what we do:- On primary, export 2 LUNs (add-vdsdev). On primary, assign these disks to the ldom in question (add-vdisk). On ldom, created mirrored zpool from these two disks. On one server (which is older) we have:- On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
lvsplit(1M)															       lvsplit(1M)

NAME
lvsplit - split mirrored LVM logical volume into two logical volumes SYNOPSIS
autobackup] suffix] PhysicalVolumeGroup] lv_path ... Remarks If the logical volume input arguments belong to a combination of volume groups version 1.0 and 2.0 or higher, the arguments might not be processed in the order they are listed on the command line. This command requires the installation of the optional HP MirrorDisk/UX software (not included in the standard HP-UX operating system) before it can be used. DESCRIPTION
The command splits a mirrored logical volume, lv_path, into two logical volumes. A second logical volume is created containing one copy of the data. The original logical volume is appropriately reset to have one fewer mirror copies. If the option is specified, the new logical volume name has the form lv_pathsuffix. If is not specified, suffix defaults to as in If more than one lv_path is specified on the command line, ensures that all logical volumes are brought offline together in one system call, ensuring predictable results among the logical volumes. All logical volumes must belong to the same volume group. The current num- ber of logical volumes in the volume group added to the number of logical volumes specified on the command line must not exceed the maximum number of logical volumes allowed in the volume group. If PhysicalVolumeGroup is specified, the offline logical volumes are created using the mirror copies on the physical volumes contained in the specified physical volume group. When a mirrored logical volume of a non-shared volume group is split into two logical volumes, a bit map is stored that keeps track of all writes to either logical volume in the split pair. If the volume group is shared, this bit map is not created. When the two logical vol- umes are subsequently merged using the bit map, if present, is used to decide which areas of the logical volumes need to be resynchronized (see lvmerge(1M)). This bit map remains in existence until one of the following conditions occurs: o The merge is completed. o One of the logical volumes is extended, reduced, or split again. o The volume group is cross-activated to shared mode (see vgchange(1M)). o The system is rebooted. The new logical volume must be checked with the command before it is mounted (see fsck(1M)). flushes the file system to a consistent state except for pipes and unlinked but open files. To rejoin two split copies of a logical volume, use the command (see lvmerge(1M)). Options and Arguments recognizes the following options and arguments: lv_path The block device path name of a logical volume. Multiple logical volumes in the same volume group can be speci- fied. The current number of logical volumes in the volume group added to the number of logical volumes speci- fied on the command line must not exceed the maximum number of logical volumes allowed in the volume group. Set automatic backup for invocation of this command. autobackup can have one of the following values: Automatically back up configuration changes made to the logical volume. This is the default. After this command executes, the command (see vgcfgbackup(1M)) is executed for the volume group to which the logical volume belongs. Do not back up configuration changes this time. The offline logical volumes will be created using the mirror copies on the physical volumes in the specified PhysicalVolumeGroup. Specify the suffix to use to identify the new logical volume. The new logical volume name has the form lv_pathsuffix. If is omitted, suffix defaults to as in Shared Volume Group Considerations For volume group version 1.0 and 2.0, cannot be used if the volume group is activated in shared mode. For volume groups version 2.1 (or higher), can be performed when activated in either shared, exclusive, or standalone mode. Note that the daemon must be running on all the nodes sharing a volume group activated in shared mode. See lvmpud(1M). When is issued, it creates the new logical volume device special files on all the nodes sharing the volume group. The device special files are created with the same name on the nodes sharing the volume group. When a node wants to share the volume group, the user must first execute a if logical volumes were split at the time the volume group was not activated on that node. The logical volumes device special files should have the same name on all the nodes sharing the volume group. LVM shared mode is currently only available in Serviceguard clusters. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Split the mirrored logical volume into two copies. Call the new logical volume Split the mirrored logical volume into two copies. The offline logical volume will be created using the mirror copy on the physical vol- umes contained in the physical volume group Split an online logical volume which is currently mounted on so that a backup can take place: Perform a backup operation, then: Split two logical volumes at the same time: Perform a backup operation on the split logical volumes, then rejoin them: SEE ALSO
lvcreate(1M), lvextend(1M), lvmerge(1M), lvmpud(1M). Requires Optional HP MirrorDisk/UX Software lvsplit(1M)
All times are GMT -4. The time now is 04:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy