Error in Making a new logical volume 1

[1500wing]

Hello,
I am attempting to creating a logical volume on an existing Volume Group (via smitty mklv). When I do, an error occurs
stating:
0516-022 lcreatelv: Illegal parameter or structure value.
0516-822 mklv: Unable to create logical volume.

The volume group is active (lsvg -o) and there are plenty of pp's available. The disks are EMC hpowerdisks and everything there is optimized. Any thoughts on this one?

Thanks
Chris

 

[bjverzal]

Run the same menu, fill in the same options. Just before you tell smit to create the lv, press F6 (or ESC-6) to see the command_to_execute.

Post the command_to_execute.

Bill.

 

[1500wing]

Hey Bill,

The output from smitty for this command is:
mklv -y'db2003tmplv' data4vg 64 hdiskpower33 hdiskpower35 hdiskpower40

Thanks
Chris

 

[bjverzal]

Ok - now comes the fun stuff...Post the following:

1. lsvg data4vg
2. lsdev -Cl hdiskpower33
3. lsdev -Cl hdiskpower35
4. lsdev -cl hdiskpower40
5. lsvg -l data4vg
6. ls -l /dev/db2*lv

Bill.

 

[1500wing]

Ok, here goes <grin>

1)lsvg data4vg
VOLUME GROUP: data4vg VG IDENTIFIER: 00010062c5d46eaa
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 7898 (126368 megabytes)
MAX LVs: 512 FREE PPs: 3579 (57264 megabytes)
LVs: 219 USED PPs: 4319 (69104 megabytes)
OPEN LVs: 208 QUORUM: 6
TOTAL PVs: 11 VG DESCRIPTORS: 11
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 11 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 128

2)hdiskpower33 Available 10-78-01 PowerPath Device
3)hdiskpower35 Available 10-78-01 PowerPath Device
4hdiskpower40 Available 10-78-01 PowerPath Device

5)data4vg:
THere are 221 lines with this command. If you really want them all listed, let me know, otherwise this string might get a little hard to read.

6)# ls -l /dev/db2*lv
brw-rw---- 1 root system 40, 12 Feb 08 2001 /dev/db2loglv
brw-rw---- 1 db2prod2 db2sysp 40, 1 Jul 17 2000 /dev/db2prodcatlv

Sorry about the wrap on the email.

Thanks Bill
Chris

 

[bjverzal]

I left 3 out...

7. lspv hdiskpower33
8. lspv hdiskpower35
9. lspv hdiskpower40

For option 5, post any lines that are not &quot;open/syncd&quot;

Bill.

 

[1500wing]

Ok, I'll paste them here:

1) lspv hdiskpower33
PHYSICAL VOLUME: hdiskpower33 VOLUME GROUP: data4vg
PV IDENTIFIER: 00010062c5d46224 VG IDENTIFIER 00010062c5d46eaa
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 33
TOTAL PPs: 718 (11488 megabytes) VG DESCRIPTORS: 1
FREE PPs: 331 (5296 megabytes)
USED PPs: 387 (6192 megabytes)
FREE DISTRIBUTION: 144..00..00..43..144
USED DISTRIBUTION: 00..144..143..100..00

2)lspv hdiskpower35
PHYSICAL VOLUME: hdiskpower35 VOLUME GROUP: data4vg
PV IDENTIFIER: 00010062c5d46413 VG IDENTIFIER 00010062c5d46eaa
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 24
TOTAL PPs: 718 (11488 megabytes) VG DESCRIPTORS: 1
FREE PPs: 372 (5952 megabytes)
USED PPs: 346 (5536 megabytes)
FREE DISTRIBUTION: 144..00..00..84..144
USED DISTRIBUTION: 00..144..143..59..00

3)lspv hdiskpower40
PHYSICAL VOLUME: hdiskpower40 VOLUME GROUP: data4vg
PV IDENTIFIER: 00010062c5d46871 VG IDENTIFIER 00010062c5d46eaa
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 19
TOTAL PPs: 718 (11488 megabytes) VG DESCRIPTORS: 1
FREE PPs: 330 (5280 megabytes)
USED PPs: 388 (6208 megabytes)
FREE DISTRIBUTION: 144..00..00..44..142
USED DISTRIBUTION: 00..144..143..99..02

 

[bjverzal]

Try this

lqueryvg -p hdiskpower33 -At
lqueryvg -p hdiskpower35 -At
lqueryvg -p hdiskpower40 -At

Bill.

 

[bjverzal]

One more thing. I was looking this up on another list I'm on...

send the results of:

lsvg -l rootvg
lsvgfs rootvg

Bill.

 

[1500wing]

I ran these commands and it appears to be fine. They all have 7898 total PPs and each query puts out 244 lines of data. If you would like me to post the data, let me know. Is there anything you've seen in your AIX musings that could possibly be the culprit?

Thanks for your help, as well!
Chris

 

[1500wing]

The following info for rootvg are:
1) # lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 64 128 2 open/syncd N/A
hd8 jfslog 1 2 2 open/syncd N/A
hd4 jfs 2 4 2 open/syncd /
hd2 jfs 124 248 2 open/syncd /usr
hd9var jfs 4 8 2 open/syncd /var
hd3 jfs 2 4 2 open/syncd /tmp
locallv jfs 3 6 2 open/syncd /usr/local
dumplv sysdump 4 4 1 open/syncd N/A

2)root@dd271e1:/ # lsvgfs rootvg
/
/usr
/var
/tmp
/usr/local

 

[bjverzal]

The hint on the other board I'm on is that this problem may be totally unrelated to the direction I've been taking you. If so, I apologize.

In the other discussion I was checking, the problem was due to a zero size filesystem in rootvg. That does not appear to be the result here though. We move on...

Just for grins and giggles, do this:

1. syncvg -v data4vg
2. synclvodm -v data4vg

Post the output.

Bill.

 

[1500wing]

Hey Bill,

I ran the sync commands and voila!! I am able to create my LV's once again. In running the sync -v data4vg the prompt returned with no output.
Running the synclvodm -v data4vg sync all the LV's within the VG (data4vg). After this, i re-ran smitty mklv and I am in business. I only ran the sync -v datavg4 prior without the synclvodm. That did the trick!

Any ideas why this gets out of sync with no warning messages or hints from the LV?

Thanks again, Bill for all the help!!

Chris

 

[bjverzal]

Honestly, there can be a plethora of reasons..

- Perhaps an interrupted LVM action (mklv/chlv) terminated with ctrl-c
- A rare condition that surfaces a bug in the LVM routines

It is really hard to say.

What is your maintenance level ?

Bill.

 

[1500wing]

I'm running AIX 4.3.3, ML 8 on this server (RS\6000). We do give DBA some priviliges in setting up additional LV's through a setuid script that we wrote. It is possible that a cntl ^C was issued or that they decided to give smitty a go and terminated from there, when they realized it wasn't going to work? It looks good now, however.

Many thanks once again!
Chris