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 . 10 Supported Libraries and Tape Drives . 12 Minimum Firmware Levels for StorNext Drives . 25 Operating Guidelines and Limitations . [. . . ] 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. Max channels has been adjusted in the StorNext database. 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. Added support for Sun/STK T10000 rev B tape drives. 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. Corrected a condition in which the service log closed stdin after a executing a process. Addressed an snmetadump ASSERT failure: Processing Error: snmetadump ASSERT failed "max_length < length" file process_metadata. c, line 860 snmetadump error at line 602 of snmetadump. c: Dump file error flag set (16): New metadump needed. 27746 27762 27865 n/a 985494, 983646 961840 Corrected a condition in which tape media was ejected on failover due to a reservation conflicted. Resolved a condition in which fsretrieve never completed. Corrected a condition in which files with a percentage symbol (%) in their names could not be recovered. Resolved Issues 23 StorNext 3. 5. 1 Release Notes 6-00431-24 Rev B July 2010 StorNext GUI and Installation Resolved Issues Table 8 lists resolved issues that are specific to the StorNext GUI or the installation process. Table 8 StorNext GUI and Installation Resolved Issues Operating System Windows All CR Number 27519 26582 SR Number 978244 779840 Description Corrected a condition in whish popup windows did not work correctly in Internet Explorer 8. [. . . ] As of release 3. 5, StorNext supports mounting file systems to a directory. For Windows Server 2003 and Windows XP you must disable the Recycle Bin for the root drive letter of the directorymounted file system. (For example: For C:\MOUNT\File_System you would disable the Recycle Bin for the C: drive. ) For Windows Server 2008 and Windows Vista you must disable each directory-mounted file system. For Windows Server 2003 or Windows XP: 1 On the Windows client machine, right-click the Recycle Bin icon on the desktop and then click Properties. [. . . ]