# mount -a
UX:vxfs mount.vxfs: ERROR: V-3-22168: Cannot open portal device: No such file or directory
UX:vxfs mount.vxfs: ERROR: V-3-25255: mount.vxfs: You don't have a license to run this program
When the vxportal kernel modules are loaded as part of the VxFS startup script (/etc/init.d/vxfs), the following files are created in the pseudo filesystem /sys.
# mount -v | grep /sys
sysfs on /sys type sysfs (rw) <<< pseudo file system type sysfs
# ls -l /sys/class/misc/vxportal <<< directory and relevant files created during loading of vxportal kernel module
-r--r--r-- 1 root root 4096 Oct 4 13:16 dev
lrwxrwxrwx 1 root root 0 Oct 4 13:16 subsystem -> ../../../class/misc
--w------- 1 root root 4096 Oct 4 13:16 uevent
As part of the system boot process, the Linux udev program (or the udev daemon process udevd) should create the /dev/vxportal device file according to the above information in the /sys filesystem. The "dev" file contains all the information needed by udev to create the /dev/vxportal device file. The information can be displayed with the udevinfo command.
# udevinfo -a -p /sys/class/misc/vxportal/dev
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/misc/vxportal/dev':
KERNEL=="dev"
SUBSYSTEM=="misc"
looking at parent device '/class/misc/vxportal':
ID=="vxportal"
BUS=="misc"
DRIVER==""
SYSFS{DEV.EN_US}=="10:32"
The udev command and the related udevd daemon are started by the following Linux startup scipt through the /etc/inittab.
/etc/inittab:
....
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
.....
/etc/rc.d/rc.sysinit:
....
/sbin/start_udev
....
If the /dev/vxportal device file is not created by udev during system boot, it may be caused by the following Bugzilla bug. Please contact Redhat technical support and see if there is a fix for it.
https://bugzilla.redhat.com/show_bug.cgi?id=151981
Bug 151981 - (IT_69402) udevd fails to create /dev files after misc_register
The problem is addressed in VxFS 5.1SP1RP4 and VxFS 6.0 (and above). The VxFS startup script is enhanced to wait for the creation of the /dev/vxportal device by udevd and display the error message "Failed to create /dev/vxportal" if udevd fails to create the device.
A temporary workaround is to create the /dev/vxportal manually after system boot.
# /bin/mknod /dev/vxportal c 10 32
This can be made automatic by adding the following command into the VxFS startup script.
/etc/init.d/vxfs:
#! /bin/sh
# $Id: vxfs.sh,v 1.1.18.3 2007/09/19 21:52:39 tko Exp $
# #ident "@(#)vxfs:$RCSfile: vxfs.sh,v $ $Revision: 1.1.18.3 $"
#
# Copyright (c) %Q% VERITAS Software Corporation. ALL RIGHTS RESERVED.
#
# chkconfig: 12345 00 99
# description: VxFS filesystem module
#
case "$1" in
start)
# Start VxFS, if installed
if [ -f /etc/vx/ted-startup -a -O /etc/vx/ted-startup ]
then
/etc/vx/ted-startup
fi
if [ -f /etc/vx/vxfs-startup -a -O /etc/vx/vxfs-startup ]
then
echo "Starting up VxFS...."
/etc/vx/vxfs-startup
fi
touch /var/lock/subsys/vxfs
# Add the following code as as a workaround for Bugzilla 151981
if [ ! -c /dev/vxportal ]
then
/bin/mknod /dev/vxportal c 10 32
if [ $? -ne 0 ]
then
echo -n "VxFS not starting due to failure creating /dev/vxportal "
exit 1
fi
fi
;;
Applies To
Veritas File System (VxFS) on Linux