SEO

Hi there,

in rootvg there's no way to extend a filesystem. Creating new ones is no
problem at all. Is chfs broken?

>chfs -a size=1048576 /home
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.

>lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 2170 (34720
megabytes)
MAX LVs: 256 FREE PPs: 1883 (30128
megabytes)
LVs: 11 USED PPs: 287 (4592
megabytes)
OPEN LVs: 10 QUORUM: 1
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 3048 MAX PVs: 10
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no

>lslv hd1
LOGICAL VOLUME: hd1 VOLUME GROUP: rootvg
LV IDENTIFIER: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX PERMISSION:
read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 16 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 1 PPs: 1
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: center UPPER BOUND: 32
MOUNT POINT: /home LABEL: /home
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes

Has anyone any ideas? I have none.

Patrick

make logical volume larger (add LP's) first, then change file system
file system /home was defined into a "previously defined" logical
volume

aixdude@yahoo.com wrote:
> make logical volume larger (add LP's) first, then change file system
> file system /home was defined into a "previously defined" logical
> volume
>
I will give that a try. But, shouldn't lvm resize the lv according to
the new fs settings? I don't know about the standard lv's but if I
define a "custom" lv and add a jfs I always define the lv with just one
lp first and resize the fs afterwards with now problems so far. The lv
is always resized properly, depending on the maxlp parameter, of course.

Seems I have an idea. Using smitty an error message occurs when trying
to expand a lv. The error message says a disk is not listed in the ODM.
The identifier describes a disk that was removed from the system some
weeks ago. The disk was removed using unmirrorvg. Seems that not all
entries of this disk were removed from the ODM. I added the disk again
and strange things appear:

>lspv
hdisk1 002091003ec20cd7 rootvg
hdisk0 00209100668b15dc rootvg

>lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE
DISTRIBUTION
hdisk1 active 2170 1883
369..380..266..434..434

>reducevg rootvg hdisk0
reducevg -d rootvg hdisk0
0516-022 lquerypv: Illegal parameter or structure value.
0516-022 lquerypv: Illegal parameter or structure value.
0516-884 reducevg: Unable to remove physical volume hdisk0.

>extendvg rootvg hdisk0
0516-696 extendvg: Physical Volume hdisk0 belongs to another volume group.

This causes all the trouble. How can I remove the faulty entries from
the ODM?

Patrick

Patrick wrote:
> Seems I have an idea. Using smitty an error message occurs when trying
> to expand a lv. The error message says a disk is not listed in the ODM.
> The identifier describes a disk that was removed from the system some
> weeks ago. The disk was removed using unmirrorvg. Seems that not all
> entries of this disk were removed from the ODM. I added the disk again
> and strange things appear:
>
> >lspv
> hdisk1 002091003ec20cd7 rootvg
> hdisk0 00209100668b15dc rootvg
>
> >lsvg -p rootvg
> rootvg:
> PV_NAME PV STATE TOTAL PPs FREE PPs FREE
> DISTRIBUTION
> hdisk1 active 2170 1883
> 369..380..266..434..434
>
> >reducevg rootvg hdisk0
> reducevg -d rootvg hdisk0
> 0516-022 lquerypv: Illegal parameter or structure value.
> 0516-022 lquerypv: Illegal parameter or structure value.
> 0516-884 reducevg: Unable to remove physical volume hdisk0.
>
> >extendvg rootvg hdisk0
> 0516-696 extendvg: Physical Volume hdisk0 belongs to another volume group.
>
> This causes all the trouble. How can I remove the faulty entries from
> the ODM?
did you try rmdev -dl hdisk0
This will remove the disk from ODM.

Greg Beeker wrote:
>
> did you try rmdev -dl hdisk0
> This will remove the disk from ODM.
>

Ah, sorry, I did not make this clear. OK, I made

unmirrorvg rootvg hdisk0
reducevg rootvg hdisk0
bosboot -a
bootlist -m normal hdisk1 ...
rmdev -dl hdisk0

Normally, this should leave the disk in defined state but unfortunately
didn't. The machine, when rebooted, recognizes hdisk0 as part of rootvg
what is a failure as the first posting shows.

Patrick

first rmdev -dl hdisk0 will take it out completely

rmdev -l hdisk0 will leave it in a defined state, a reboot or cfgmgr
will attempt to bring it back

Second, can you post the following:
lsvg -p rootvg
lslv -l hd1
lspv -l hdisk0
lspv -l hdisk1
ipl_varyon -v

also a bootinfo -b
lquervg -Ltp hdisk0
lquervg -Ltp hdisk1

Hi,

you won't believe it, the error is gone.

For I did not have any idea where the prob comes from I decided just to
ignore it. I removed hdisk0 again. I still wasn't able to extend the
filesystem after that. I removed the disk from the system physically and
added a new one. OK, running cfgmgr, extendvg ...

After extending and mirroring the rootvg the problem vanished.

Don't ask, it's an computer ...

Patrick