patch upgrade disabled online jfs... Do I only need to reinstall PHKL_18543?

[Jack C. Mahaffey]

Just got doing some patching on one of my servers using patches from custom patch manager.

Online Advanced JFS apparently got disabled when PHLK_18543 go re-installed.

I've been reading the forums and "I think" the fix is to re-install PHKL_18543. Is this correct? I'm pretty much done with all patches at this point.

I've seen major emphasis on being sure that the patch reinstall option is not set to true.


Here's my approach: Let me know if it will work:

1 Go to hp site and get phkl_18543 and all dependencies for phkl_18543 as a *.zip file.
2 ftp the file to the server and unzip it.
3 Create the depot with the create script.
4 Run swinstall against the newly created depot. Take swinstall defaults.
5 Server will reboot.
6 Once server is up, Online JFS Advance should work.
7 Run cpm_collect.sh to collect current patches.
8 ftp .fs file on HP site.
9 Run custom patch manager against cpm file .fs.
10 Anlalyze current patches. Select recommended patches if any identified.
11 Finish custom patch manager activities and create a .sh file.
12 ftp the .sh file to the server and run make_depot
13 Run swinstall one final time to install any remaining patches.
14 Done

[Robert-Jan Goossens · Accepted solution]

Hi,

Take a look at this doc,

Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000065679117

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000065679117

Hope it helps,

Robert-Jan.

[James R. Ferguson]

Hi Jack:

Have a look at Technical Knowledge Base document #KBRC00001453. PHKL_18543 and OnlineJFS functionality (namely the 'vxadv' kernel driver) are intimately related.

Regards!

...JRF...

[Michael Steele_2]

First, you should probably call the Response Center and get the latest procedure on phkl_18543 since its been very controversial. And hopefully HP now has a better fix in place then the old one, which was restore every affected or restore from a make_recovery tape.

Here is the current fix from the patch, but again, I suggest you call the response center:

http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHKL_18543&context=hpux:800:11:00#Special%20Installation%20Instructions:

#############################################

Special Installation Instructions:
If PHKL_18543 is installed on a system that does not have
Advanced VxFS, then the Advanced VxFS driver 'vxadv' will be
commented out of the /usr/conf/master.d/vxfs file as follows:

* Disabling AdvJournalFS: vxadv vxadvc 10 100 ...

The following note will be logged in the swagent.log file:

NOTE: "AdvJournalFS" product is now disabled. Any vxadv driver in
the system file will be ignored. If you install the 11.00
version of "AdvJournalFS", you must again install this patch,
PHKL_18543.
(The reinstall* options must be set to false - the default.)

If the Advanced VxFS product is subsequently installed, PHKL_18543
must be reinstalled as specified in the note above, otherwise the
following warning will occur when creating a kernel and the Advanced
VxFS features will not be available:

WARNING: No such device, tunable, or cdio vxadv.
Ignoring the following line.
vxadv

Please apply this patch along with command patch PHCO_13411.
Failure to do so, ie. applying one without the other, will
result in fsck failure, or even fsck corrupting the
filesystem.

The new features in PHKL_13552 are only supported for
V-Class 64-bit systems. Non-V-Class systems can install
this patch with no impact to those systems. The following
patches rely on PHKL_13552 to enable certain features:

PHCO_13606: SAM recognition of new tunables
PHCO_13571: insf, mksf, lssf recognize new devices
PHCO_13494: fbackup/frecover recognize new devices

To enable large record support on V-Class systems, you will
need to set the following tunables:
scsi_maxphys 16777215
st_large_recs 1

To enable failed data overruns where stape reads are shorter
than the actual record size, use:
st_fail_overruns 1

Installing PHKL_17040 on PCI based systems will add diag1 to
the /stand/system file and create the /dev/diag/diag1 device
file. Removing PHKL_17040 will delete diag1 from
/stand/system file and remove the /dev/diag/diag1 device
file from the system. Installing/Removing any patch
superseding PHKL_17040 will leave the system in the state
it was prior to installing the patch.

It may be necessary to boot on a backup kernel to recover
from the boot hang before installing this fix.