Sponsored Content
Operating Systems AIX logical volume partially mirrored Post 302206360 by bakunin on Tuesday 17th of June 2008 01:49:09 PM
Old 06-17-2008
The part of the map output you posted seems to be ok, but this:

waslv jfs2 277 477 3 open/syncd /usr/WebSphere

tells me, that not everything is ok at all. The first number - 277 - is the number of logical partitions and since every logicl partition should map to two physical partitions the second number should be 554 ^= 277*2. As this is not the case something must have fone wrong with the mirroring and a simple "syncvg" will most probably not cure it.

I would first find out what has gone wrong (nothing in your post indicates what tht could have been, just that it happened), then i would unmirror the LV, then mirror it again, taking care that whatever the reason was it doesn't happen again.

If this general advice doesn't help you, please post the complete output of "lsvg -l rootvg" and "lsvg rootvg", so that we could further help you.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

checking to see if logical disks are mirrored.

I have AIX 5.1 I ran these commands and was not able to see what disk were mirrored to what. I thought this is what I should do? lslv -m rd |more lslv -m db |more I get a error stating that it can't find or in the device configuation databse. Is there another way to look? I have a physcal... (1 Reply)
Discussion started by: rocker40
1 Replies

2. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

3. AIX

Moving a Logical Volume from one Volume Group to Another

Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies

4. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

5. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

6. 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

7. HP-UX

[Solved] How to extend a mirrored logical volume?

Want to extend the /home filesystem: Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol4 262144 260088 2056 99% /home root@server:./root # vgdisplay vg00 --- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 11 Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies

8. AIX

Position of the logical volume on the physical volume

Hello everyone, I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created. When I say region I mean: outer edge - outer middle - center - inner middle and inner edge. Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies

9. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

hi, I want to create a volume group of 200 GB and then create different file systems on that. please help me out. Its becomes confusing when the PP calculating PP. I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
PDISK(8)						    BSD System Manager's Manual 						  PDISK(8)

NAME
pdisk -- Apple partition table editor SYNOPSIS
pdisk [-acdfhilLrv] [--abbr] [--compute_size] [--debug] [--fname] [--help] [--interactive] [--list device] [--logical] [--readonly] [--version] [device ...] DESCRIPTION
pdisk is a menu driven program which partitions disks using the standard Apple disk partitioning scheme described in "Inside Macintosh: Devices". It does not support the Intel/DOS partitioning scheme supported by fdisk(8). Supported options are: -a --abbr Abbreviate the partition types shown in the partition list. -c --compute_size Causes pdisk to always ignore the device size listed in the partition table and compute the device size by other means. -d --debug Turns on debugging. Doesn't add that much output, but does add a new command 'x' to the editing commands that accesses an eclectic bunch of undocumented functionality. -f --fname Show HFS volume names instead of partition name when available. -h --help Prints a short help message. -i --interactive Causes pdisk to go into an interactive mode similar to the MacOS version of the program. -l --list device List the partition tables for the specified devices. -L --logical Show partition limits in logical blocks. Default is physical blocks. -r --readonly Prevents pdisk from writing to the device. -v --version Prints the version number of pdisk. Editing Partition Tables An argument which is simply the name of a device indicates that pdisk should edit the partition table of that device. The current top level editing commands are: C (create with type also specified) c create new partition d delete a partition h command help i initialize partition map n (re)name a partition P (print ordered by base address) p print the partition table q quit editing (don't save changes) r reorder partition entry in map s change size of partition map t change the type of an existing partition w write the partition table Commands which take arguments prompt for each argument in turn. You can also type any number of the arguments separated by spaces and those prompts will be skipped. The only exception to typeahead are the confirmation prompts on the i and w commands, since if we expect you to confirm the decision, we shouldn't undermine that by allowing you to be precipitate about it. Partitions are always specified by their number, which is the index of the partition entry in the partition map. Most of the commands will change the index numbers of all partitions after the affected partition. You are advised to print the table as frequently as necessary. The c (create new partition) command is the only one with complicated arguments. The first argument is the base address (in blocks) of the partition. Besides a raw number, you can also specify a partition number followed by the letter 'p' to indicate that the first block of the new partition should be the same as the first block of that existing free space partition. The second argument is the length of the parti- tion in blocks. This can be a raw number or can be a partition number followed by the letter 'p' to use the size of that partition or can be a number followed by 'k', 'm', or 'g' to indicate the size in kilobytes, megabytes, or gigabytes respectively. (These are powers of 1024, of course, not powers of 1000.) The third argument is the name of the partition. This can be a single word without quotes, or a string sur- rounded by single or double quotes. The type of the created partition will be Apple_UNIX_SVR2, which is the correct type for use with NetBSD. This command will prompt for the unix filesystem slice to set in the Block Zero Block bits. The C command is similar to the c command, with the addition of a partition type argument after the other arguments. Choosing a type of Apple_UNIX_SVR2 will prompt for the unix filesystem slice to set in the Block Zero Block bits. The i (initalize) command prompts for the size of the device. The n (name) command allows the name of a partition to be changed. Note that the various "Apple_Driver" partitions depend on the name field for proper functioning. We are not aware of any other partition types with this limitation. The r (reorder) command allows the index number of partitions to be changed. The index numbers are constrained to be a contiguous sequence. The t (change partition type) command allows the type of a partition to be changed. Changing the type to Apple_UNIX_SVR2 will prompt for the unix filesystem slice to set in the Block Zero Block bits. The w (write) command writes the partition map out. In order to use the new partition map you must reboot. SEE ALSO
fdisk(8), newfs(8) HISTORY
The pdisk utility was originally developed for MkLinux. AUTHORS
Eryk Vershen BUGS
Some people believe there should really be just one disk partitioning utility. Filesystem volume names are out of place in a partition utility. This utility supports HFS volume names, but not volume names of any other filesystem types. The --logical option has not been heavily tested. pdisk will first try to use lseek(2) with SEEK_END to compute the size of the device. If this fails, it will try a binary search using lseek(2) and read(2) to find the end of the device. This has been observed to fail on some raw disk devices. As a workaround, try using the block device instead. pdisk should probably read the disklabel using the DIOCGDINFO ioctl(2) to get the device size instead. BSD
April 24, 2003 BSD
All times are GMT -4. The time now is 06:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy