Filter
Top Products
April 2006, ADIC 5
Windows Memory Requirements
The SNFX 1.3 release has a number of performance enhancements that enable it to better react to
changing customer load. These enhancements come with additional memory requirements. Because the
Windows operating system has unusual memory resource limitations it is sometimes necessary to adjust
StorNext memory tuning settings to provide optimal operation.
When running multiple file systems in the Windows environment the StorNext memory tuning parameters
must be adjusted or the machine will run out of memory. This can be seen is by bringing up task manager
and watching the Non-paged tag in the Kernel Memory pane in the lower right hand corner. Microsoft
warns that the maximum amount of non-paged memory consumed cannot exceed 256MB. However, the
actual amount varies depending on your configuration. For example, on a machine with 256MB of memory
ADIC testing has found that non-paged memory must not exceed 96MB.
Non-paged memory is the most critical resource limitation but not the only one. For example, Microsoft
warns that paged memory consumption must not exceed 470MB. Similarly, the actual amount also varies
depending on configuration.
Memory exhaustion can be observed in the following ways:
• commands failing
• messages in the system log about insufficient memory
• fsmpm process mysteriously dying
• repeated FSM reconnect attempts
• messages in the application log and cvlog.txt file about socket failures with the status code (10555)
which is ENOBUFS
• messages in the system log about ConvertExtent failed with error 20
HP-UX SNFX clients: A minimum of 1 GB of RAM is required.
Solaris SNFX clients: A minimum of 512 MB of RAM is required.
Linux SNFX clients: A minimum of 512 MB of RAM is required.
Windows 2000
Windows Server 2003
Windows XP
SNFX clients: A minimum of 512 MB of RAM is required.
Network LAN using TCP/IP
(all clients and servers
must be interconnected)
For the SNFX metadata traffic, ADIC requires that a separate, dedicated,
switched Ethernet LAN be used.
SAN SNFX clients: An FC-HBA or equivalent SAN communication device
where the storage is visible and accessible to multiple SAN clients.
SNFX does not support multiple hosts connected through an FC hub
device because the resulting propagation of Loop Initialization Protocol
resets can cause data corruption.
Client Hard Disk SNFX requires 200 MB of hard disk space for binaries, documentation,
configuration, and log files.
Disk Drives SNFX only supports the file system when it is running on FC-3 SCSI
drives.
System/Component Requirement