Release Notes

20 Limitations
The following is an example of an error message that may be written to the FSE error log file after a bus
reset and the consequent FSE tape media rewind:
Other messages that can be displayed are:
Proper operation of the FSE implementation in a SAN environment is guaranteed only if the SAN switch or
bridge is configured in such a way that it propagates bus reset errors. The errors can then be detected and
handled appropriately by FSE, and data loss can be prevented.
Reusing file systems for newly configured FSE partitions
FSE does not allow existing HSM file systems to be assigned to newly configured FSE partitions. You can
configure a new FSE partition and use the fsepartition --add command only if a native file system
with non-HSM directories and files is specified in the FSE partition configuration file. Such a file system can
be any of the supported native file systems, provided that it has not been used as an HSM file system
before.
Linux specific
On Linux platform, the supported native file system type is Ext3.
Windows specific
On Windows platform, the supported native file system type is NTFS.
CAUTION: Data loss will occur during FSE operation if you try to reuse a file system that was previously
used as an HSM file system by assigning it to a new FSE partition.
You can however reuse disk space occupied by an HSM file system by deleting the file system and creating
a new one in its place.
Linux specific
You can create a new file system by running the mkfs command.
Windows specific
You can create a new file system by creating and formatting a new disk volume with the Computer
Management tool.
NOTE: Upgrade from a previous FSE release to current FSE release preserves both the existing FSE
partitions and HSM file systems, so the above limitation does not apply for the upgrade process.
Linux-specific limitations
Special file types are not supported
The FSE implementation does not support handling of special file types. On Linux platform, the following
file types are not supported:
• char devices
• block devices
CRITICAL ERROR: Internal error. Contact support. (5: MAJOR INTERNAL
ERROR: Data corruption detected. 'Counted medium position (395405) is
different from actual (12897). Job: 20050607000206 Medium/volume:
000391/1').
(5. MAJOR INTERNAL ERROR: Data corruption detected. 'Data loss detected.
Medium was overwritten. See error log. Medium/volume: 000391/1')
(5. MAJOR INTERNAL ERROR: Data corruption detected. 'Medium position
changed to 0. Aborting. See error log. Medium/volume: 000391/1')