User manual QUANTUM STORNEXT 3.5.1 RELEASE NOTES REV B

[. . . ] StorNext 3. 5. 1 Release Notes Product Date StorNext® 3. 5. 1 July, 2010 Contents Purpose of this Release . All rights reserved. 6-00431-24 Rev B, July 2010 Quantum, the Quantum logo, Scalar, and StorNext are registered trademarks of Quantum Corporation, registered in the U. S. Specifications are subject to change without notice. StorNext 3. 5. 1 Release Notes 6-00431-24 Rev B July 2010 Purpose of this Release StorNext 3. 5. 1 is a maintenance release that improves behind-the-scenes performance and corrects issues identified in previous releases. This document lists issues that were resolved for this release, currently known issues, and known operating limitations. [. . . ] Corrected a condition in which running cvfsck did not fix corruption as adequately as the 3. 1. 2 version. Dump_rj was modified to collect information about a specific inode or a range of lsn entries. Added the ability to place orphaned inodes into a specified directory inode. Added Quality of Service (QOS) support for Distributed LAN clients and servers. Addressed an FSM panic that occurred because trans_write: space reservation was too small for type 6. Addressed a condition in which data corruption sometimes occurred when bringing UP a DOWN stripe group. Corrected a condition which caused metadata dumps to fail on systems with multiple metadata stripe groups. Corrected a condition in which running an external API (ExtApiGetSgInfo) returned a static stripe group status instead of a dynamic stripe group status. Corrected a condition in which performing a metadata dump caused problems for directories in multi metadata stripe groups. Corrected a condition in which metadata on a file system with multiple stripe groups could not be correctly restored. Corrected a system panic caused by multiple clients accessing a file at the same time. Resolved a metadata dump failure that occurred during the initial optimization phase. 27484 27772 985224 968024 27862 871834, 877874 996254 27932 27964 n/a 27967, 27943 27982 n/a n/a Resolved Issues 21 StorNext 3. 5. 1 Release Notes 6-00431-24 Rev B July 2010 StorNext Storage Manager Resolved Issues Table 7 lists resolved issues that are specific to StorNext Storage Manager. Table 7 StorNext Storage Manager Resolved Issues Operating System Linux CR Number 26753 SR Number 896404 Description Corrected a condition in which conflicting CONF manifest numbers prevented StorNext system backup from running successfully. Corrected a condition which caused a disconnection and error message due to an erroneous call to FindNicServiceName. Windows 27167 832794 All 25314 871834, 877874 Corrected a condition in which a file system containing several offline stripe groups prevented truncation from occurring. Note: If you applied the workaround for this issue before installing release 3. 5. 1, you must "undo" the workaround by using the StorNext GUI to reset the truncation values to either their original or default values. 26054 878862, 842072, 942922 909624 887578 Corrected a condition in which running fsmedcopy -r failed when the destination media was full. Corrected a condition in which some large minsetsize settings did not trigger stores. Corrected a condition in which Storage Manager filled tapes with wasted space if the inode class was incorrect. Corrected a condition which caused a fs_dmapi fault due to long file names. Addressed a condition in which LibManager processes could become defunct if SL_TAC_MASK is not set to the default value in /usr/adic/MSM/logs/ log_params. 26292 26385 26388 26552 26576 909878 n/a 927346 26579 26624 26809 933846 n/a 947962 Corrected a condition in which fs_fmover hung due to a StorNext database issue. Addressed a condition in which fsretrieves from the same media had to wait for the unmount delay. 22 Resolved Issues StorNext 3. 5. 1 Release Notes 6-00431-24 Rev B July 2010 Operating System All CR Number 26855 26856 26949 26950 SR Number n/a n/a n/a 948026, 946116, 958332 n/a n/a 795978 787774 n/a 985224 Description Addressed snmetadump failures on systems with multiple metadata stripe groups. Corrected a condition in which fsmedlist output showed media as protected when they were not. Addressed a condition in which HA conversion did not move the database after OS conversion. Corrected a condition that caused StorNext tables to become corrupted. For more information, see StorNext Product Alert 29 Support for the Sun/STK SL3000 library has been added to StorNext. Cvgather/snapshot now gathers capacity and usage 26954 26957 26979 26991 27178 27485 information. Improved logic used when determining the Storage Manager API host name. Corrected a condition that prevented the t_parent process from shutting down. [. . . ] When you are upgrading to StorNext 3. 5 from a release prior to version 3. 0, you must uninstall StorNext before installing. After uninstalling you must reboot, install StorNext 3. 5. Operating Guidelines and Limitations 37 StorNext 3. 5. 1 Release Notes 6-00431-24 Rev B July 2010 Operating System / Affected Component Windows Description If you are using the StorNext client software with Windows Server 2003, Windows Server 2008, Windows XP, or Windows Vista, turn off the Recycle Bin in the StorNext file systems mapped on the Windows machine. You must disable the Recycle Bin for the drive on which a StorNext file system is mounted. Also, each occurrence of file system remapping (unmounting/mounting) will require disabling the Recycle Bin. [. . . ]