3.7.0 HP StorageWorks HP Scalable NAS File Serving Software provisioning guide for Oracle HP Scalable NAS (AG513-96013, October 2009)

To disable the SizingActions script, execute the following steps on each server
in the cluster:
1. Go to the directory containing the SizingActions script:
# cd /etc/opt/hpcfs
2. Run the following command:
# chmod 444 SizingActions
3. Reboot the node to ensure that the SizingActions parameters are cleared
from the system. The SizingActions script will now be inactive at system
start.
Clearing NLM locks after a power failure on an NFS
client
With NLM locking, when NFS clients holding byte-range locks experience a sudden
power failure, there is no time for the locks to be cleared as they would be during a
normal shutdown. To remedy this, the statd process on the NFS client keeps track
of servers whose files contain locks once held by this NFS client. On the NFS client,
the directory /var/lib/nfs/statd/sm contains files whose names are IP addresses
of the NFS servers that once held locks for the client. If the power fails, these files
are used by the statd process when it restarts to send an SM Notify command to
each of these servers, releasing all locks previously held by this NFS client.
If an NFS client is powered down while holding a lock and cannot come back up,
the locks for this client will continue to be held on the server. This is expected behavior
for the NFS/NLM/SM protocols. These locks will persist until either the NFS server
is rebooted or, in the case of a held lock obtained via a virtual host, the virtual host
is failed over to another NFS server node. With either approach, clients accessing
that NFS server via virtual hosts will be transitioned gracefully to other servers.
However, any other NFS client accessing the NFS server using its physical IP address
will need to remount if the NFS server should need to reboot.
There are known NFS client issues where a client reboot does not cause locks to be
released. In this case, use the same method of virtual host failover (or NFS server
reboot) to clear the locks.
After any server reboot or virtual host failover, all lock holding NFS clients have a
45-second grace period to reclaim their locks. Should a new client machine be used
to host the application, no locks will be available for this 45-second grace period.
HP Scalable NAS File Serving Software provisioning guide for Oracle 29