User manual QUANTUM STORNEXT FX 2.0 RELEASE NOTES REV A

[. . . ] StorNext FX 2. 0 Release Notes Contents 0 Purpose of this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Operating System Level Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Resolved Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] Resolved a condition that locked up the system after starting FSM services. Added improvements to the cvdbset script. Reduced the size of the free space tree structures. Corrected a condition in which starting FSM while backups are running caused the restore journal to be disabled. Resolved a condition in which data corruption occurred when device mappings from a SAN environment changed while CVFS is operational. Reduced FSM CPU consumption in transaction buffer processing. Corrected a situation in which cvmkfs didn't catch an error when devices are rearranged underneath it. Corrected an error related to XSan 2. 0 which caused client core dumping during a mount attempt. Corrected a condition in which mounting failed due to the kernel misinterpreting the number of valid paths. Corrected an error allocating new directory blocks due to copious copying and moving files to a different directory. Corrected a condition in which running the proxy who command caused the fsmpm process to spin endlessly on the target machine, repeatedly asking the kernel for the proxy client list. 23320 All 15910 16012 16019 n/a n/a n/a 717096 16040 n/a 16041 16078 16094 16142 16378 16664 n/a n/a n/a n/a 710517 712214 23083 n/a Resolved Issues 10 StorNext FX 2. 0 Release Notes Document 6-01663-03 Rev A April 2008 Operating System All CR Number 23122 SR Number n/a Description Addressed a condition in which it was not possible to stop an FSM if the IP addresses change. Running the cvadmin stop command caused failure with the error message "FSM is not local. " Resolved directory cache invalidation errors when dragging and dropping files from a Mac to a Windows machine. Added support for the DS4700 array with inquiry string "IBM 1814" as a known "LSI" type disk. Corrected the error message that appears if opening /dev/cvfsctl fails with EPERM 23143, 23302 and 23309 23230, 23323 and 23339 23411 and 16587 720143 725383 715497 Known Issues The following table lists known issues in this release of StorNext FX, as well as associated workarounds where applicable. 0 Operating System Macintosh CR Number 24577 SR Number n/a Description Adding a Macintosh client to an existing Xsan cluster and then rebooting the metadata controller causes a change in the . auth_secret file on all Macintosh systems in the cluster. Unless you modify the . auth_secret file on your SNFX client, errors could result. Workaround (if applicable) After you add a Macintosh client to an existing Xsan cluster, you must copy the . auth_secret file from the Macintosh systems to SNFX clients. Known Issues 11 StorNext FX 2. 0 Release Notes Document 6-01663-03 Rev A April 2008 Operating System All CR Number 23474 SR Number n/a Description Due to the way SNFS performs writebehind caching for buffered I/O and flushes buffers to disk, you might receive some of the following system log entries, depending on your system configuration: I/O error on cookie 0x36a11a cvfs error 'IO error' (0x3) os status code 0x3 blkno 0xaad9c000 offset 0x5a40000 count 0x4000 resid 0x0 I/O path in error [hostid: 5 lun: 0 path < /dev/sdb>] quiesced for 300 seconds I/O error on cookie 0x36a11a cvfs error 'IO error' (0x3) os status code 0x3 blkno 0xaad9c000 offset 0x5a40000 count 0x4000 resid 0x0 Workaround (if applicable) When these messages appear, you should check the system log for driver-level errors that generally indicate data loss due to SAN hardware problems. Note: When random I/O is performed, there is also a rare case that can generate a spurious I/O error with a status code of 0x2. For example: I/O error on cookie 0x36a11a cvfs error 'Not found' (0x2) os status code 0x2 blkno 0xaad9c000 offset 0x5a40000 count 0x4000 resid 0x0 These errors can be safely ignored. Operating Guidelines and Limitations 0 The following table lists updated information and guidelines for running StorNext FX, as well as known limitations in this release. (Some of the guidelines and limitations listed apply to previous versions of StorNext upon which StorNext 2. 0 is based. ) Operating System / Affected Component IRIX Description StorNext supports only SGI 64-bit versions of IRIX on operating systems that use the SGI version of the QLogic QLA2200 or QLA2310 FC-HBAs. 32-bit applications (programs compiled without 64-bit) support may experience problems working with files with inode numbers greater than 2147483648. 32-bit applications may also encounter problems when dealing with files greater than 2TB in size, This issue is not unique to StorNext, but may be encountered by some legacy applications when working with SNFS on IRIX. Operating Guidelines and Limitations 12 StorNext FX 2. 0 Release Notes Document 6-01663-03 Rev A April 2008 Operating System / Affected Component IRIX Description On many versions of IRIX, the root crontab contains the following entry which is used to remove old application crash dumps and temporary mail files: find / -local -type f '(' -name core -o -name dead. letter ')' -atime +7 -mtime +7 exec rm -f '{}' ';' If StorNext file systems are mounted, they will be traversed by this find command which can have a dramatic impact on the performance of other applications currently using these file systems. To prevent the traversal of StorNext file systems, modify the find command so it reads: find / -local '(' -type d -fstype cvfs -prune ')' -o -type f '(' -name core -o -name dead. letter ')' -atime +7 -mtime +7 -exec rm -f '{}' ';' Linux StorNext does not support the use of loopback IP addresses other than 127. 0. 0. 1. SUSE Enterprise Linux 10 systems sometimes have an entry for 127. 0. 0. 2 in the /etc/hosts file. [. . . ] For example, on managed servers, I/O to and from tape now goes through the buffer cache. To revert to the settings used in previous releases, change the following mount options on StorNext clients: auto_dma_read_length=65537 auto_dma_write_length=65537 Hot re-zoning of SAN fabrics is not supported. StorNext File System is incompatible with third-party portmappers. In StorNext 3. 0, the buffercachemin and buffercachemax parameters are deprecated and are replaced by buffercachecap. [. . . ]