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 |
| |
|
|
|
| ||
|
|
| become unkillable when |
| |
|
|
| unmapping a shared memory |
| |
|
|
| segment. In turn, this prevents an |
| |
|
|
| SNFS file system from being |
| |
|
|
| unmounted. |
| |
|
|
|
|
| |
| 54345 | n/a | Unsupported XMEM function; error | n/a | |
|
|
| implies no space, but there is |
| |
|
|
| plenty of space. |
| |
|
|
|
|
| |
| 33986 | n/a | During a StorNext upgrade, if you | Reboot the machine and | |
|
|
| encounter a DSM failure that | repeat the upgrade | |
|
|
| resembles the following output: | process. | |
|
|
| SNFS UPGRADE 2.6.1(48) Status | NOTE: This may be caused | |
|
|
| 1) Upgrade 2.6.1(48) perl | by an inability to unmount | |
|
|
| the file system. Check the | ||
|
|
| Complete | ||
|
|
| log for details. | ||
|
|
| 2) Upgrade 2.6.1(48) GUI | ||
|
|
| Complete |
| |
|
|
| 3) Upgrade 2.6.1(48) apache |
| |
|
|
| Complete |
| |
|
|
| 4) Upgrade 2.6.1(48) DSM |
| |
|
|
| Failed |
| |
|
|
| Check /tmp/SNFS.install.log |
| |
|
|
| log file for errors. |
| |
|
|
| Do you wish to continue (Yes |
| |
|
|
| or <No>)? No |
| |
|
|
|
|
| |
IRIX | 34763 | 308348 | The cvdb | The | |
|
|
| work with IRIX. | supported at this time. | |
|
|
|
|
|
12 | April 2006, ADIC |
