lvlnboot -v

[Rob Reynolds]

The output from lvlnboot -v is returning the following error

Illegal instruction(coredump). Its not a problem when I run it as lvlnboot -v vg00. Its seems to core dump when accessing a VG that has 132 disks or 264 w/ Alternate links...

This is preventing us from running make_recovery.

[Rita C Workman]

I'm not positive, but you may have hit on your problem.

What I am aware of - is that a volume group can contain 1 to 255 physical disks.

So I'm thinking that, like you mentioned, with alternate links that puts you at 264 physical disks...so that may be the problem.

Just a thought,

[Ovidiu D. Raita]

That's for sure because a buffer overflow on the lvlnboot source code. Having in mind that the max number of PVs (not alternate links) within a VG is 256 and disregarding the fact that 256*2=512 some programmer might have allocated only 256 units for the buffer and if you have more than 128 PV you've got a problem. You could try ( if you have down time) to deactivate that volume group and run make_recovery ( or just lvlnboot -v).

I while ago I came across a similar issue with OmniBack-XP256 integration agent that had room for only 100 PVs in the buffer and they recompiled a new agent after they increased the figure.

Good luck,
Ovidiu

[rajsri]

Hi Rob ,
I guess this problem is fixed in PHCO_20870.

goodluck