Hub/Switch Installation Guide

Chapter 2 HPSS Planning
62 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
2.5.8 XFS
XFS for Linux is an open source filesystem from SGI based on SGI’s XFS filesystem for IRIX.
HPSShasthecapabilitytobackendXFSandtransparentlyarchiveinactivedata.ThisfreesXFSdisk
to handle data that is being actively utilized, giving users theimpressionof aninfinitely large XFS
filesystem that performs at near-native XFS speeds.
It is well suited to sites with large numbers of small files or clients who wish to use NFS to access
HPSS data. However, the files can only be accessed through XFS (or NFS via XFS) interfaces and
cannotbeaccessed with HPSSutilitiessuch asparallelFTP. Therefore,datatransferperformance is
limited to XFS speeds.
2.6 HPSS Server Considerations
Servers are the internal components of HPSS. They must be configured correctly to ensure that
HPSS operates properly. This sections describes key concepts and notions of the various servers
and their impact on system use, operation, and performance.
2.6.1 Name Server
The HPSS Name Server (NS) maintains a data base in five Encina SFS files. An SFS relative
sequenced file is used to store data associated with NS objects. (NS objects are bitfiles, directories,
symbolic links, junctions and hard links.) The four other files are SFS clustered files. Two of these
filesstoretextdataandACLentries,andtheremainingtwofilesareSFSclusteredfilesthatareused
to store fileset information.
The total number of objects permitted in the name space is limited by the number of SFS records
allocatedto theNS.Referto Section2.10.2.4 fordetailsonselecting thesize ofthenamespace. With
thisreleaseofHPSS,provisionshavebeenmadeforincreasingthesizeofthenamespacebyadding
additional Name Servers, storage subsystems, or by junctioning to a Name Server in a different
HPSS system (seeSection 11.2.3: FederatedName Space on page 279of the HPSS Management Guide).
Refer to Section 10.7.3: Name Server Space Shortage (page 272) in the HPSS Management Guide for
information on handling an NS space shortage.
The NS uses DCE threads to service concurrent requests. Refer to Section 6.5.1: Configure the Basic
Server Information (page 263) for more information on selecting an appropriate number of DCE
threads. The NS accepts requests from any client that is authenticated through DCE; however,
certainNSfunctionscanbe performedonlyiftherequestisfromatrustedclient.Trustedclientsare
those clients for whom control permission has been set in their CDS ACL entry for the NS. Higher
levels of trust are granted to clients who have both control and write permission set in their CDS
ACL entry. Refer to Table 6-3: Basic Server Configuration Variables on page 266 for information
concerning the CDS ACL for the Name Server.
The NS can be configured to allow or disallow super-user privileges (root access). When the NS is
configured to allow root access, the UID of the super-user is configurable.
Multiple Name Servers are supported, and each storage subsystem contains exactly one Name
Server.Though theserversareseparate, eachName Serverin agivenDCE cellmust sharethesame
metadata global file for filesets.