Growing Filesystems 1 server will, 1 will not

[Roland Rebstock_1]

All, I have hpux 11.0 and on one system I can grow a filesystem on the fly without unmounting it but on another sam wants to unmount it? Here is the swlist information from both servers.. Any IDEA's, see attached

[Pedro Cirne]

Hi,

You can grow a filesystem on-line if you have Online JFS.

Check:

swlist -l product|grep -i online

Enjoy :)

[A. Clay Stephenson]

Using The Force, I sense that while OblineJFS 3.3 is installed on the bad server is is not yet licensed. 3.3 was the first version to require run-time licensing in order for OnlineJFS to function. You can confirm this with a vxlicense -p.

[Simon Hargrave]

You attached no files however I would guess that you don't have Online JFS installed - this is a requirement if you want to grow filesystems on the fly.

[Roland Rebstock_1]

The working server has the following patches. But how can I tell if the working systems is licensed? there is no vxlicense command on the server?

PHKL_22393 1.0 VxFS 31 OnlineJFS cumulative patch
PHKL_24745 1.0 VxFS 31 OnlineJFS cumulative patch

The non working server does not have the patches?

[Roland Rebstock_1]

could it be that the working server is because its 3.1?

[A. Clay Stephenson]

Note that the good server does not have VxFS 3.3 installed. If 3.3 is installed, it overrides the behavior of 3.1 and to revert to your 3.1 OnlineJFS you must swremove the 3.3; a better answer would be to install the newer OnlineJFS. As long as all you vxfs filesystems are version 3 or lower, you can safely remove 3.3 but if you are running any version 4 vxfs filesystems then 3.1 will not be able to mount them. You can determine the version of a vxfs filesystem by running the vxupgrade /mountpoint command BUT DO NOT SPECIFY -n version so that the only action is to display the current filesystem version. Man vxupgrade for details.

[Roland Rebstock_1]

im removeing jfs3.3 from the non working server and rebooting now, both systems have version 3 filesystems.

[Roland Rebstock_1]

Still, I cannot grow on the fly on the 1 system but the other extends a filesystem without any umounting

[A. Clay Stephenson]

It would be nice to know if this is a SAM issue or VxFS; it appears that neither of these boxes have been patched on a regular basis unless this is a condensed swlist. I would check to see if the OnlineJFS has been installed but not configured.

Compare these outputs on both boxes:

swlist -l fileset -a state B3929BA

If they are the same then I would try manually extending the filesystems. If that works then you need a cumulative SAM patch.