Краткое содержание страницы № 1
Release Notes
Product: StorNext FX 1.3
SNFX Client Operating Systems:
SGI IRIX 6.5.26, 27, and 28 (MIPS 64-bit)
Solaris 9 and 10 (SPARC 64-bit)
Red Hat Enterprise Linux Advanced Server 3.0,
Updates 4, 5, and 6 (32-bit Intel and AMD; 64-bit for Itanium, Opteron, and EM64T)
Red Hat Enterprise Linux Advanced Server 4.0, Updates 1 and 2
(32-bit Intel and AMD; 64-bit Itanium, Opteron, and EM64T)
Red Hat Linux 9.0 (32-bit)
SUSE Linux Enterprise Server 9, Service Pack 2 (SLES);
(32-bit Inte
Краткое содержание страницы № 2
Purpose of this Release StorNext FX (SNFX) 1.3 includes several new features and enhancements that extend its capabilities. These release notes describe these new features and enhancements, as well as currently known issues and issues that were resolved for this release. These notes also provide drive and auxiliary firmware compatibility information. SNFX is a client only version software that is licensed to run in Apple managed environments and used with an Apple metadata controller. If is
Краткое содержание страницы № 3
Operating System Level Requirements The following table lists the required operating system levels required to successfully operate SNFX 1.3. SNFX 1.3 Requirements Operating System Operating System Levels Platform AIX 5.2, 5.3 (Power Architecture 64-bit) HP-UX 11i v2 (PA-RISC and 64-bit Itanium) IRIX 6.5.26, 27, and 28 (MIPS 64-bit) Red Hat Linux Red Hat Enterprise Linux Advanced Server 3.0 - Updates 4, 5, and 6 (32-bit Intel and AMD; 64-bit Itanium, Opteron, and EM64T) Required kernels: U4 -
Краткое содержание страницы № 4
Operating System Operating System Levels Platform Windows Server 2003 Service Pack 1 (32-bit Intel and AMD) Windows XP Service Pack 2 (32-bit Intel and AMD) Certified System Components This table lists certified system components that support SNFX 1.3. Component Description Browsers Netscape 7.x Microsoft Internet Explorer 5.5 and later Mozilla 1.4 and later FireFox 1.0 and later HBA Emulex LP8000, LP850, LP9000, LP90002 QLogic: QLA2200, QLA2310, QLA2340, QLA2342 NFS Versions 3 Multi-pathing Fa
Краткое содержание страницы № 5
System/Component Requirement 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 SNFX clients: A minimum of 512 MB of RAM is required. Windows Server 2003 Windows XP Network LAN using TCP/IP For the SNFX metadata traffic, ADIC requires that a separate, dedicated, (all clients and servers switched Ethernet LAN be used. must be interconnected) SAN SNFX clie
Краткое содержание страницы № 6
The solution is to adjust a few parameters on the Cache Parameters tab in the SNFX control panel (cvntclnt). These parameters control how much memory is consumed by the directory cache, the buffer cache, and the local file cache. As always, an understanding of the customer's workload aid in determining the correct values. Tuning is not an exact science, and requires some trial-and-error to come up with values that work best in the customer's environment. The settings in the Cache Paramete
Краткое содержание страницы № 7
Configuring LDAP The following information describes how to configure the new StorNext LDAP feature in addition to outlining recent changes to Windows configuration tools. Using LDAP SNFX 1.3 introduces support for Light Directory Access Protocol, or LDAP (RFC 2307). This feature allows customers to use Active Directory/LDAP for mapping Windows User ID's (SIDs) to UNIX User ID/Group ID's. Changes to "Nobody" mapping As with previous releases, if a Windows user cannot be mapped to a Unix ID, t
Краткое содержание страницы № 8
Navigating to the Windows File System Control Parameters pane > Authentication tab gives the administrator the ability to disable the NIS/PCNFSD mapping on a client by client basis by checking LDAP. Domain Server Requirements The domain server must be at least Windows 2000 or above to support RFC 2307 mapping. Client Requirements Mapping is done by searching the domain server that the Windows machine is a member of. The user must be logged in under the user account owned by that domain server.
Краткое содержание страницы № 9
Operating CR SR Description System Number Number IRIX 38875 310052 On IRIX, Mmap fails for files larger 2 GB. 51662 n/a POSIX sparse file support defaults to yes in StorNext 2.7. NOTE: This change can have a negative performance impact. The previous behavior can be achieved with an explicit deactivation of posix-sparse-file support. Linux 24245 221686 On Linux, license key MAC address enumeration fails with multiple NIC's. 34919 n/a Linux ioctl call must use copyin/copyout. 35317 n/a ld com
Краткое содержание страницы № 10
Operating CR SR Description System Number Number All 18144 179324 Pathing method definition not included in c:\cvfs\help\cvfs_config.htm file. 33490 296206 Client panicked after running cvfs stop. 33544 n/a Installation procedures needs a 64-bit operating system check. 33601 n/a Windows rename failed with full pathname greater than 128 characters. 33726 n/a Bad value passed to "cvdb -R" causes panic. 33747 288626 SNFS - failure to start fsmpm hangs. 33834 n/a cvntclnt fails to map drives. 341
Краткое содержание страницы № 11
Operating CR SR Description System Number Number All 50103 n/a In previous versions of StorNext, the modification time of a file was not updated when a file size was explicitly changed using the truncate(2) system call on UNIX or the _chsize() function on Windows. With StorNext 2.7, this has been corrected and setting the size of a file will cause the modification time of the file to be set to the current time. 51688 n/a With StorNext 2.7, the output of the cvlabel -l command has changed.
Краткое содержание страницы № 12
Known Issues The following tables list known issues in this release of StorNext. File System Issues The following CRs are specific to the StorNext File System. Operating CR SR Description Workaround System Number Number AIX 51306 n/a Using the umount command can Make sure that all cause applications to fail. applications are stopped before invoking umount. 52300 n/a Due to a potential bug in AIX (PMR n/a 32512,033), applications using memory-mapped I/O may hang and become unkillable when
Краткое содержание страницы № 13
HP-UX 38359 n/a FC cable pull does not initiate Use the SecurePath Fibre failover. Channel driver. 38892 n/a Cache coherency between nodes As of the StorNext 2.5 with applications that use mmap release date, HP-UX 11iv2 can potentially see data corruption. applications using mmap(2) may lose some data under some circumstances. If a file is mmaped for PROT_WRITE and another thread or process uses mmap(2) and then munmap(2) on the file or performs non-mmap I/O, for example, read(2)/wri
Краткое содержание страницы № 14
Solaris 51308 n/a Solaris NFS clients get I/O errors Do not use the cp -p when using the cp -p command. command which attempts to copy ACLS not supported by StorNext. 52120 n/a Newly labeled disks are not usable Reboot the system. in SNFS on Solaris 9 or 10 until system reboot. Windows 14254 n/a In a Windows/UNIX environment, Verify that path names are using path names longer than 220 not longer than 220 characters may cause procedures characters. to fail under all versions of Microsoft W
Краткое содержание страницы № 15
All 34784 n/a When performing a cvcp n/a command from a Windows client against a file with international characters, a “cannot find file” error is returned. 34903 n/a Breaking an Ethernet connection n/a causes a disconnect that invalidates locks (file locking). 37589 n/a The cvadmin command does not Manually add entries for list all file system servers. This each host listed in problem can be identified by the fsnameservers file to the following syslog message: /etc/hosts file. ERR NSS: E
Краткое содержание страницы № 16
All 42761 n/a Unix clients can create symbolic Delete or rename symbolic links in StorNext file systems that links only on UNIX clients. are usable on Windows clients if they meet the following criteria: • The link is relative (it does not start with a '/' character) • The link is valid (it points to file or directory that is visible on the Windows client) In particular, symbolic links to files can be used to read or write the target file, and symbolic links to directories can be used
Краткое содержание страницы № 17
All 53141 n/a An error message may be 1 On the metadata generated if you have a file system controller node, run the configured with one or more LUNs cvfsck -t that are "short-labeled", that is, command to list the LUNs that have a raw capacity names of files or greater than 4294967295 sectors, directories allocated in but have been labeled with a the restricted area reduced capacity of 4294967295 ('trespassing' files). sectors (the maximum number of 2 On a client machine -- se
Краткое содержание страницы № 18
Limitations This table lists the limitations that have been discovered in this release of SNFX. Operating System/ Description Component Affected IRIX SNFS uses 64-bit inode numbers. 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 so
Краткое содержание страницы № 19
Operating System/ Description Component Affected Solaris On Solaris, by default, the /usr/lib/fs/nfs/nfsfind script is run nightly by the cron daemon. This script contains a find command that traverses any local file system that is exported (shared) via NFS. If the running of this script is interfering with the performance of processes accessing StorNext file systems, it can be modified to skip them. To do so, add the following line to the find command in the script: '(' -type d -fstype cvf
Краткое содержание страницы № 20
Operating System/ Description Component Affected All With SNFX 1.3, a change has been made to the way that the Reserved Extents performance feature affects free space reporting. In the previous release, SNFS would reserve a certain amount of disk space which would cause applications to receive an out of space error before the disk capacity reached 100%. In the current release, this reserved space is treated as allocated space. This allows applications to perform allocations until the file
