3.7.0 HP StorageWorks HP Scalable NAS File Serving Software release notes for Linux (AG513-96006, October 2009)

DescriptionDefect
QLogic Switch login can cause HP Scalable NAS failures
HP Scalable NAS will not start if you are logged into a QLogic FibreChannel switch and
admin start is set. A message such as the following will appear:
Switch address is not responding to SNMP SET requests. Verify the
configured community string has SNMP write privileges.
The FibreChannel switches are not responding to SNMP requests.
Verify that the switches are configured to accept SNMP access from
this server using the configured community string. The FibreChannel
switches and HP Scalable NAS must be configured with the same
community string.
If you log into the switch with admin start while HP Scalable NAS is running, this switch
problem can affect fencing operations and may cause the cluster to hang.
Workaround. Avoid putting the switch into admin start mode while HP Scalable NAS is
running. If it is necessary to use this mode while HP Scalable NAS is running, limit the use
of the mode as much as possible.
7435
Partition tables can be constructed incorrectly
When partitioning a disk, make sure the first partition begins at an offset beyond sector one
on the disk. This is necessary because the Linux kernel supports a number of different partition
table formats, and some of them make use of sector one in addition to sector zero. If sector
one is a data sector in a partition, it is possible that user data written to that sector may
subsequently cause the Linux kernel to “recognize” a different partition table format than is
actually there, which could result in the partitions being “constructed” incorrectly by the kernel.
8346
RDAC driver problem can cause I/O requests to hang
When the Host Bus Adapter is returning errors because of BUSY or QUEUE_FULL conditions,
the RDAC driver may leave I/O requests on the physical device's request queue, resulting in
errors stating that a node is stalled waiting for locks.
Workaround. Reduce the HBA queue depth to a value of 8 or less. See the procedure “Reduce
the HBA queue depth” in the HP Scalable NAS File Serving Software administration guide
for more information.
15575
Bonding driver issues kernel error messages
The Linux network bonding driver creates "container" devices to which actual physical network
links are "enslaved." The behavior of the bonding driver depends on communication between
it and the underlying physical network device drivers, with names such as bnx2, tg3, or
e1000. Out-of-date, mismatched, or malfunctioning device drivers may make the bonding
driver appear to be the primary source of kernel error messages.
One such source of this behavior might be the mistaken installation of the Intel e1000 (PCI)
driver in place of the newer e1000e (PCI Express or PCIe) driver or vice versa. If the bonding
driver is reporting kernel errors or is found to be the source of kernel panics, insure that the
underlying device drivers are the proper type and revision for the associated network hardware
device.
23770
Using Oracle with HP Scalable NAS
Oracle servers and their databases are supported in the following ways using clusters formed with
HP Scalable NAS 3.7.0:
• Running the Oracle instance on Linux 64-bit servers in the cluster.
• Running on Oracle Servers using files exported via NFS from the cluster.
18