Filter
Top Products
Managing the AMASS File System
6-00028-01 Rev A Troubleshooting Tools -5
Operating Issues
The following table lists operating issues:
Operating
System
Issues
All AMASS supports a file pathname limit of 1023
characters. For example, if files are going under
/archive/oursitefiles on AMASS, then the length of this
string (21 characters) must be subtracted from 1023
(1023-21=1002). Consequently, succeeding file
pathnames can be a total of 1002 characters in
length.
All AMASS does not support running binaries in the
AMASS file system.
All The Macintosh operating system uses a separate
data stream called a resource fork to store icons and
other resource information. When AMASS archives
this file, the UNIX system truncates this resource fork
without generating any messages.
All When AMASS lists file names, it uses the metadata
file from the AMASS File System Database stored on
the UNIX server. However, Windows 95 and Windows
NT operating systems use executable files with icons
stored as part of the file. Consequently, to display
these icon-embedded file names that AMASS has
archived, AMASS must reload the file from the library.
IRIX 6.2
Using
NFS 3
Using the UNIX
xfsdumps command to transfer large
files (800MB and greater in size) over NFS Version 3
may degrade AMASS performance.
Acceptable performance is attained if the AMASS
cache block size is set to 50MB with 9 (or more) dirty
blocks and on NFS a write buffer size is set to 32KB.