vmount: a system call received a parameter that is not valid

[tkozel]

Hi,
I am have removed a couple boxes out of our nis environment in order to set up a small network to be used off site for a few months. I removed the nis and all automount configurations, created new dir's for mounting and exported them. When I try to mount from another box I get the error, 1831-008 vmount:a system call received a parameter that is not valid. These machines are ibm 43p 150's running aix 433ml10. They where all created from the same image using nim. Inside my nis environment they automount or hard mount, whatever I choose without error. But as soon as I remove the nis that is when the error occurs. I seached this site but was not able to find a answer. Any help would be wonderful.
Thanks

 

[ademeter]

Remove or reconfigure your NIS configuration:
smit ypconfigure -> Remove NIS ...

Check your /etc/filesystems file. Attach the stanza for the failing filesystem as a reply.

Check your /etc/vfs file. It should look like this:

# @(#)vfs @(#)77 1.29 src/bos/etc/vfs/vfs, cmdfs, bos520 5/2/02 09:51:55
# IBM_PROLOG_BEGIN_TAG
# This is an automatically generated prolog.
#
# bos520 src/bos/etc/vfs/vfs 1.29
#
# Licensed Materials - Property of IBM
#
# (C) COPYRIGHT International Business Machines Corp. 1985,1989
# All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# IBM_PROLOG_END_TAG
#
# COMPONENT_NAME: CFGETC
#
# FUNCTIONS:
#
# ORIGINS: 27
#
# (C) COPYRIGHT International Business Machines Corp. 1985, 1995
# All Rights Reserved
# Licensed Materials - Property of IBM
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# this file describes the known virtual file system implementations.
# format: (the name and vfs_number should match what is in <sys/vmount.h>)
#
# The standard helper directory is /etc/helpers
#
# name vfs_number mount_helper filsys_helper
#
# Uncomment the following line to specify the local or remote default vfs.
%defaultvfs jfs nfs
#
cdrfs 5 none none
procfs 6 none none
jfs 3 none /sbin/helpers/v3fshelper
jfs2 0 /sbin/helpers/jfs2 none
nfs 2 /sbin/helpers/nfsmnthelp none remote
sfs 16 none none
nfs3 18 /sbin/helpers/nfsmnthelp none remote
cachefs 17 /sbin/helpers/cfsmnthelp none remote
udfs 34 /sbin/helpers/udfmnthelp none
cifs 37 /sbin/helpers/mount_cifs none
autofs 19 /sbin/helpers/aufsmnthelp none
fsm 15 /sbin/helpers/fsmvfsmnthelp none

 

[dbrig]

I have experienced a similiar problem. It usually occurs after NIM'ing a system. The solution was to:

cp /usr/lpp/bos.net/inst_root/sbin/helpers/nfsmnthelp /sbin/helpers

You may want to check to make sure the two files are different before doing the copy. Apparently when a system gets NIM'ed it will use the nfsmnthelp from the SPOT which may not be the same level as the image used to BOS install. Hope this helps....