Cluster volume does not mount due to "failure reason = 22" or "failure reason = 17"

  • Document ID:7000228
  • Creation Date:28-Apr-2008
  • Modified Date:27-Apr-2012
    • Micro Focus Products:
      Cluster Services
      Open Enterprise Server

Environment

Novell Open Enterprise Server (Linux based)

Situation

When trying to online a cluster resource the volume will not mount.
It will fail on the "ncpcon mount" line in the cluster script.

In the /var/run/ncs/resourcename.load.out a message is logged:

volumename: failure reason = 22
or
volumename: failure reason = 17

Resolution

The "volumename: failure reason = 22" error means the volume name is already in use in the ncp cache.
The "volumename: failure reason = 17" error means the volume ID is already in use in the ncp cache.

There is already a volume with that name or volume ID in the NCP cache.
This is most likely caused by an entry in the /etc/opt/novell/ncpserv.conf file.
It will look like this:
   VOLUME volumename /mountpoint

To fix "failure reason 22":
  1. Comment this line out of the ncpserv.conf, if it exists.
  2. Offline the cluster resource.
  3. Do a "cluster leave" to exit the cluster.
  4. Restart edirectory with "rcndsd restart". This will clear the NCP cache that holds the bad volume information.
  5. Then join the cluster again with "cluster join".
  6. Then online the cluster resource with "cluster online RESOURCENAME"
To fix "failure reason 17"
  1. Check each of the resource load scripts for the volid that it loads and make sure they are unique.
  2. Modify the load scripts and then offline and online the resource.

Additional Information

You can see what the ncp cache has in it by doing the following at the server console:
  1. "ncpcon log all" this will turn on logging for NCP
  2. Type "ncpcon volumes"
  3. "ncpcon log error" turn logging back to the defaults.
  4. look at the /var/opt/novell/log/ncpserv.log file and you will see the volume names and ID

In the ncpserv.log file you will see output similar to the following.  The cluster volume name and volume ID has been bolded.

<ncpConsoleReply><listVolumes><volume><name>SYS</name><status>3ld</status><volumeNumber>0</volumeNumber></volume>

<volume><name>_ADMIN</name><status>536870914ld</status><volumeNumber>1</volumeNumber></volume>

<volume><name>VOL1</name><status>1075838977ld</status><volumeNumber>2</volumeNumber></volume>

<volume><name>VOL10</name><status>1075838979ld</status><volumeNumber>3</volumeNumber></volume>

<volume><name>CLUSTERVOL</name><status>1084227587ld</status><volumeNumber>254</volumeNumber></volume></listVolumes>
<result value="0"></result>
</ncpConsoleReply>