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

DescriptionDefect
Third-party MPIO software must discover devices
When third-party MPIO software such as EMC PowerPath or IBM RDAC is used, the third-party
MPIO software must discover and present storage devices to the operating system before HP
Scalable NAS is configured or started.
If HP Scalable NAS is started and the third-party MPIO software has not previously discovered
the devices, HP Scalable NAS will make a “best effort” to discover them. In some cases, HP
Scalable NAS will initiate a single reboot. HP Scalable NAS will not start if it cannot discover
the devices. The administrator must then determine why the MPIO devices have not been
discovered and resolve the issue.
7519
Virtual host can cause route change
When a virtual host is instantiated it uses the network mask of the interface upon which it is
activated. This can cause a unexpected route change if the virtual host address was intended
for some other interface on another network or if the virtual host address is mistyped.
For example, the following command adds the 10.10.1.100 address on the 10.11.1.1
interface.
mx vhost add 10.10.1.100 10.11.1.1
If the 10.11.1.1 interface had a netmask of 255.255.0.0, then the traffic for the 10.10/16
subnet would be directly routed to the 10.11/16 network for this server rather than being
routed to a gateway on the 10.11/16 network.
8290
URL in HTTP service monitor can cause virtual host to fail
The URL assigned to an HTTP service monitor should not reference the virtual host with which
the HTTP service monitor is associated. If the virtual host is down, the HTTP service monitor
will not be able to make a connection to the virtual host address and will also be down. A
down service monitor on a virtual host then tends to keep the virtual host from ever being
instantiated.
8335
Volume Properties window does not show snapshot properties
The Volume Properties window shows properties for a basic or dynamic volume as well as
the filesystem mounted on the volume, but does not show properties for a snapshot mounted
on the volume.
To see information about a snapshot, use the utilities provided with the web management
appliance.
8477
ls can be slow on busy filesystems
The ls command, and other utilities that touch or examine files, can be slow when run on
directories, or parents of directories, that are busy on other nodes.
If ls is aliased to add any options such as --color=tty or -l, the ls command will need
to examine the stat data on the files in the directory being listed. If those files are busy on
other nodes, the other nodes will need to flush their data and wait while ls reads the files.
Because this procedure can cause the command to be slow, we recommend that you remove
the ls options.
9557
File operations are slow
If examining or touching a file takes a long time when another node is writing to the file, you
can use the command iostat -x on the node writing to the file to determine whether the
queue depth and average wait times on the partition containing the file have become large
enough to cause slowness.
9557
8