Sponsored Content
Operating Systems AIX Unable to rmlvcopy on jfs2log rootvg Post 302990506 by rbatte1 on Friday 27th of January 2017 10:41:56 AM
Old 01-27-2017
With the disk still Active, perhaps the log volume copy that is alive is actually on the failing disk. Try to sync the logical volume and then see if you can drop the copy on hdisk1. Because it's the only mirrored LV left, you can get away with synchronising the whole volume group.

If it refuses, try to remove the logical copy without specifying a disk. If it drops the copy on hdisk4 then use migratepv to move the LV from hdisk1 to hdisk4



Robin
 

9 More Discussions You Might Find Interesting

1. AIX

Cloned Rootvg

New Question: The purpose of an alternate disk install is in my opinion to have a ready-to-use-backup and i've read that it is possible to install filesets or software on the cloned disk for testing purposal while the normal system is still running. The question is: how do you tell AIX (5.2... (5 Replies)
Discussion started by: kvanelshocht
5 Replies

2. AIX

mirror rootvg

Hello I have a question I have a box with Aix 5.3 with rootvg on mirror. I deleted a filesystem and I create a new one to install some software but when I type lsvg -l rootvg all my filesystems has mirror unless the new one. My question is I can mirror this fs only ??? or I have to... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies

3. AIX

Anyone know how to access rootvg?

I'm trying to troubleshoot an issue with an AIX system here. I have no experience with system administration of IBM stuff. Our local admin is ... um ... not available at this time. I found something online that said enter service mode - How the heck do I do that??? Why is IBM stuff lack proper... (2 Replies)
Discussion started by: bbbngowc
2 Replies

4. AIX

extendvg and rootvg

When attempting to extend rootvg to a new physical disk I received the following message: 0516-1162 extendvg: Warning, The Physical Partition Size of 64 requires the creation of 1093 partitions for hdisk5. The limitation for volume group rootvg is 1016 physical partitions... (4 Replies)
Discussion started by: jyoung
4 Replies

5. AIX

mirroring rootvg

I would like to konw wheather below steps are sufficient for mirroring rootvg. extendvg rootvg hdisk1 mirrorvg rootvg bootlist -m normal hdisk0 hdisk1 bosboot -ad hdisk0 bosboot -ad hdisk1 or anything needs to be added. (7 Replies)
Discussion started by: manoj.solaris
7 Replies

6. AIX

rootvg mirrored

I want to increase the size of /tmp by 1GB I know that the command is chfs -a size=+1G /tmp But the rootvg is mirrored and when I do a lsvg -p rootvg, I could see 2 disks. Will there be any impact if I increase the size of /tmp when the rootvg is mirrored ? Please advise. (1 Reply)
Discussion started by: newtoaixos
1 Replies

7. AIX

Convert rootvg to scalable

hello everyone, I have an AIX6.1 machine and i want to convert the rootvg to scalable format because i need to increase the size of specific file systems and i cannot do it with its current state. I know that in order to perform this operation the volume group must be varied off so is there a way... (5 Replies)
Discussion started by: omonoiatis9
5 Replies

8. AIX

Reducing / on rootvg

The root filesystem was mirrored, someone/something stopped mirroring, and increased / and /home to ridiculous values (/ got increased to 102gb and its only using 4.3gb, so 98gb is free). Can I reduce the / (/dev/hd4) filesytem down WITHOUT corrupting the the OS? I would do a: chfs -a size=10g... (6 Replies)
Discussion started by: mrmurdock
6 Replies

9. UNIX for Beginners Questions & Answers

AIX - mirror a jfs2log

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
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 06:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy