vxenablef: errno 19

[Ceesjan van Hattum]

Hi,
I installed OnlineJFS (hpux 11.00.01) with
it's licensecode, but when i do a
/sbin/fs/vxfs3.3/vxenablef -e full
i get
Unable to enable VxFS feature VXFS. errno 19

What is errno 19 ??
Regards,
Ceesjan van Hattum

[Jeff Schussele · Accepted solution]

Hi Ceesjan,

Err 19 is ENODEV - No Device.
I suspect that you don't have the OnLine JFS driver vxadv in the kernel. Check that vxadv is in /stand/system & then check the driver state with SAM. Make sure vxadv is IN. If it's not then change the state, relink & reboot.

HTH,
Jeff

[RAC_1]

swverify OnlineJFS

swlist -l product -a state OnlineJFS

Anil

[Geoff Wild]

Check:

vxlicense -p

Is vxportal in kernel?
grep vxportal /stand/system

Rgds...Geoff

[Geoff Wild]

Just found case I had - which was same thing - definately was vxportal issue:

# /sbin/fs/vxfs/vxenablef -a
Unable to enable VxFS feature HP_OnLineJFS. errno 19


lsdev |grep vxportal
97 97 vxportal unknown

Should be 97...

To rebuild kernel:

# cd /stand/build
# /usr/lbin/sysadm/system_prep -v -s system
This extracts a current copy of your system file into /stand/build/system

Use kmsystem(1M) to modify the system file and system description files.

# kmsystem -c y -S ./system vxportal
NOTE: Redo that same command for each and every driver from the list of drivers above

Build the kernel:
mk_kernel -s system
The mk_kernel command creates /stand/build/vmunix_test, a kernel ready for testing.

Move the old system file and kernel so if anything goes wrong, you still have a bootable kernel:
mv /stand/system /stand/system.prev
mv /stand/vmunix /stand/vmunix.prev
mv /stand/dlkm /stand/dlkm.vmunix.prev

Move the new system file and new kernel into place, ready to be used when you reboot the system:
mv /stand/build/system /stand/system
kmupdate /stand/build/vmunix_test

kmupdate(1M) initiates the automatic move of the specified kernel file, together with its associated directory containing related files, to /stand/vmunix and /stand/dlkm/,
respectively, during shutdown.
It also automatically saves the old kernel and its associated directory to /stand/vmunix.prev and /stand/dlkm.vmunix.prev/, respectively.


Reboot the system using the shutdown -r (1M) command (not reboot(1M)).


Rgds...Geoff

[Jeff Schussele]

Hi Geoff,

I don't think that vxportal is the trouble.
I believe Ceesjan has an HP-UX 11.0 system - inferred by the version of OnLine JFS 11.00.01
OnLine JFS for 11.11 should be B.11.11
And vxportal is not used in 11.0

Rgds,
Jeff

[Geoff Wild]

Sorry Ceesjan - Jeff is correct - my solution is for 11.11 - not 11.0 - misread your question....I only keyed on errno 19 - which I had for same reason last month - but on a 11i server...

I have a couple of 11.0 machines left - with OnlineJFS...


Do a:

kmsystem | grep vx

You should see:

vxadv Y -
vxbase Y -
vxportal N -


If no vxadv, then you may need to re-install OnlineJFS - again.

I would place a call to HP Support.

Rgds...Geoff

[Cheryl Griffin]

Definitely check what is installed. The error indicates the OnLineJFS product is not correctly installed.

# swlist -l fileset JFS

You should see a number of JFS 3.3 entries.
Post your output here.

[Ceesjan van Hattum]

I've seen some wierd things on my system, but i'll come back to it tomorrow.

CU

[Ceesjan van Hattum]

Hi,
vxadv is in /stand/system, but i can't find it in 'sam' nor in 'kmsystem'.
kmsystem gives me this:
vxbase Y -
vxfs N -
vxfs33_q4_syms N -
vxportal N -
vxportal33 N -
,while 'sam' say this:
vxbase IN IN
vxfs IN IN
vxfs33_q4_syms IN IN
vxportal33 IN IN
(no vxportal there..)
SO.. who is telling me the truth...?
I understand that i have to reinstall
OnlineJFS..
The 'swverify' gives me no errors but
lots of warnings: superceed patches etc.

Together with my supportdesk, i'll try
to find a way to get the patching right.
But one question leaves me puzzled:

How can i manage to let 'sam', /stand/system and kmsystem tell me the same.. should these three be in sync with each other ??

Regards,
Ceesjan
(ps. Points will be awarded later, don't worry).

[Cheryl Griffin]

Possibly SAM couble be showing you the drivers are IN Pending a kernel rebuild.