Well, it does not twig any grey matter - but, I am wondering if your concurrent VG information is still the "old" style that was developed for SSA way back when, or if it is the new style - now called "extended concurrent".

Maybe there are new volume groups - which would make them new style by default.

And, unfortunately, I do not know of a command to see which format is in use. The old format was onl;y supported with SSA disks, and I think in AIX 5.2 both were supported, and in AIX 5.3, or at some tech level, all support for SSA concurrent format was removed.

Note: HACMP only works with the extended format, and - afaik, if HACMP is not installed, the extended concurrent is only a capability - not an active feature. The bos.clvm.enh fileset is there to make the creation/update possible while the cluster.clvm fileset adds the needed code for the heartbeat network.

The standard questions: oslevel -s; have you submitted a PMR to IBM?

Like you, I am surprised that there are errors reported in lvmt.log. I would not expect any activity with the cluster fileset installed.

what storage system is behind this? local, SAN, NAS??

Dear All,

I am not sure if anyone has seen this before. It certainly has got me stumped....

After the system is left idle for 12 or so hours, I come back to it, login as root and all looks good. EXCEPT, the Volume Group details are not accessible.

lsvg <vgname> returns no output, just goes to next prompt
same for lsvg -l or lsvg -p.
It is as if the VG's are lovked, but insteag of waiting, the prompt returns back with no output and no errors.

I can "wake up" the VG with:  chvg -u <vgname>
That works.
Nothing in error log.

This is a H70 running AIX 5.3 TL-11 (latest)
It was converted from AIX.4.3 by a Migration Installation.

Has anyone seen this before?
After 20+ years of AIX admin work, I have never experienced this.

Regards,
mark Remenyi