File Formats archiver.cmd(4) NAME archiver.cmd - Sun StorEdge SAM-FS archiver commands file SYNOPSIS /etc/opt/SUNWsamfs/archiver.cmd AVAILABILITY SUNWsamfs DESCRIPTION Commands for controlling the archiver are read from /etc/opt/SUNWsamfs/archiver.cmd, which is the archiver commands file. The archiver.cmd file must be free from errors, or the archiver does not execute. Use the archiver -lv command to check the archiver.cmd file for syntax errors. When it is free from errors, use the samd config command to reconfigure the daemons. Archive Sets and associated media are defined in the archiver command file. Archive Sets are the mechanism that the archiver uses to direct files in a samfs file system to media during archiving. All files in the file system are members of one and only one Archive Set. Characteristics of a file are used to determine Archive Set membership. All files in an Archive Set are copied to the media associated with the Archive Set. The Archive Set name is simply a synonym for a collection of media volumes. Files are written to the media in an Archive File, which is written in tar format. The combination of the Archive Set and the tar format results in an operation that is just like using the command find to select files for the tar command. In addition, the meta data (directories, the indices of segmented files, and the removable media information), are assigned to an Archive Set to be copied to media. The Archive Set name is the name of the file system. (See mcf(4)). For segmented files, the archivable unit is the segment, not the entire file, so the properties and priorities apply to the segments themselves rather than to the entire file. The index of a segmented file contains no user data and so is assigned to the meta data archive set. Symbolic links are considered data files for archival purposes. Each Archive Set may have up to four archive copies defined. The copies provide duplication of files on different media. Copies are selected by the Archive Age of a file. The archiver command file consists of directive lines. In this man page, the archiver directives are separated into the following sections and subsections: General Directives section Archive Set Assignments section Archive Copy Definitions section Archive Set Copy Parameters section Archive Set Copy Parameters - General Archive Set Copy Parameters - Priority Archive Set Copy Parameters - Scheduling Archive Set Copy Parameters - Recycling VSN Pool Definitions section VSN Associations section Each of these lines consists of one or more fields separated by white space. Leading white space is ignored. Everything after a '#' character is ignored. Lines may be continued by using '\' as the last character on the line. All parameter settings and Archive Set definitions apply to all file systems (global) until a file system directive is encountered. Thereafter, the settings and definitions apply only to the named file system (local). The directives archmax, bufsize, drives, notify, and ovflmin can only be global and hence are not allowed after the first fs= directive. GENERAL DIRECTIVES SECTION General directives are identified by the '=' character in the second field or no additional fields. archmax = media target_size Set the Archive File maximum size for media media to target_size. Files to be archived will be placed on the media in a single Archive File of length less than or equal to target_size. If a single file is greater than target_size, then this restriction does not apply. Sizes appropriate to the media are used by default. archivemeta = state Set the meta data archiving state on or off. state may be "on" or "off". Meta data archiving is on by default. background_interval = time Set the interval between background scans to time. The default is 24 hours. If time is a multiple of days, the background scan will be performed at the background_time . background_time = hhmm Set the time of day for the background scan to hhmm local time. The default 0000 (midnight). bufsize = media buffer_size [ lock ] Set the archive buffer size for media media to buffer_size * dev_blksize, and (optionally) lock the buffer. For media, specify a valid media type from the list on the mcf(4) man page. For buffer_size, specify a number from 2 through 1024. The default is 4. This value is multiplied by the dev_blksize value for the media type, and the resulting buffer size is used. The dev_blksize can be specified in the defaults.conf file. The lock argument indicates whether or not the archiver should use locked buffers when making archive copies. If lock is specified, the archiver sets file locks on the archive buffer in memory for the duration of the sam-arcopy(1M) operation. This avoids paging the buffer, and it can provide a performance improvement. The lock argument should be specified only on large systems with large amounts of memory. If insufficient memory is present, it can cause an out of memory condition. The lock argument is effective only if direct I/O is enabled for the file being archived. By default, lock is not specified and the file system sets the locks on all direct I/O buffers, including those for archiving. This directive can also be specified on an archive set basis by placing the -bufsize=buffer_size and -lock directives between params and endparams directives. For more information on this, see the -bufsize=buffer_size and -lock directives mentioned later on this man page. For more information on dev_blksize, see the defaults.conf man page. For more information on enabling direct I/O, see the setfa(1) man page, the sam_setfa(3) library routine man page, or the -o forcedirectio option on the mount_samfs(1M) man page. drives = library count Set the number of drives to use for archiving on library (the library family set name as defined in the mcf) to count. The archiver will use only count number of drives in library to create archive copies. This directive prevents the archiver from using all drives in a library and possibly interfering with staging. The default value is the actual number of drives in the library. Example: drives = gr50 3 examine = method Set the file system examination method to method. Files in a file system are examined using the method defined by this directive. method may be one of: scan Scan the file system in the traditional manner. The first scan is a directory scan, all successive scans are inode scans. scandirs All scans are directory scans. scaninodes All scans are inode scans. noscan No periodic scans are performed. Files are examined when they change. The default examine method is noscan. fs = file_system Start local definitions for file system file_system. All parameter settings and Archive Set definitions will apply only to this file system. This directive may be followed by copy definitions to define multiple copies for the file system meta data. The defaults are no local definitions and one archive copy for the file system data. interval = time Set the interval between archive operations to time. The default time is 10 minutes. logfile = filename Set the name of the archiver log file to filename, specified as an absolute pathname. The archiver log file contains a line for each file archived. The line contains information about the file that includes the date, time, media, volume, Archive Set, and the name of the file. Note that it is possible to have a separate log file for each file system (by placing a "logfile =" definition after a "fs =" definition). The default is no log file. notify = filename Set the name of the archiver event notification script file to filename. This file is executed by the archiver to allow the system administrator to process various events in a site specific fashion. The script is called with a keyword for the first argument. The keywords are: emerg, alert, crit, err, warning, notice, info, and debug. Additional arguments are described in the default script. The name of the default script is: /etc/opt/SUNWsamfs/scripts/archiver.sh. ovflmin = media minimum_size Set the minimum size of a file which will require more than one volume for media media to minimum_size. Files to be archived that are smaller than this size will be placed on only a single volume of the media. Files that are larger than this size will be allowed to be written to multiple volumes. If not specified, volume overflow will not take place. scanlist_squash = state Control the sam-arfind scanlist consolidation. state may be "on" or "off". If files in two or more subdirectories with the same parent directory need to be scanned by sam-arfind at a much later time, the scan entries can be consolidated if state is on. The sam- arfind scanlist consolidation is off by default. setarchdone = state Control the changing of the state of the 'archdone' flag for a file when the file is examined by sam- arfind. state may be on or off. When all archive copies for a file have been made, the archdone flag is set for that file to indicate that no further archive action is required. The archdone flag is used by the archiver only during an inodes scan to avoid looking up the path name for the inode. Setting archdone for files that will never be archived can be a time consuming operation during directory scans impacting performance when large directories are scanned. Therefore, this will no longer be done by default. To get the previous behavior, set the state to on. The default value of state is off for examine = scandirs and examine = noscan. This option does not affect setting the state of archdone when archive copies are made. wait The archiver will not begin archiving until it receives a start command from archiver, samu, or samcmd. This is a mechanism to allow other activities to be performed before archiving begins. The wait may be applied globally or to one or more file systems. The default is no waiting. timeout = [ operation | media ] time External events may cause the archiving I/O operations to stop for indefinite periods of time. This will hamper timely archiving of other files that are not affected by the external delays. Timeouts are provided for the operations that may get stopped. The timeout values for the write operation may also be specified for individual media. operation may be one of: read Reading the file from the disk. Default = 1 minute. request Requesting the archive media. Default = 15 minutes. stage Staging the file to be archived. Default = 0 (no timeout). write Writing to the archive media. Default = 15 minutes. ARCHIVE SET ASSIGNMENTS SECTION Archive Set assignments are made by describing the characteristics of the files that should belong to the set. The statements that do this are patterned after the find(1) command. The Archive Set name is the first field, followed by the path relative to the Sun StorEdge QFS file system mount point. The path may be enclosed in quotation mark characters, for instance, "project/gifs". Within the quoted string, the usual character escapes are allowed, including octal character value. The remaining fields are either the file characteristics for membership in the set, or controls for the set. It is possible that the choice of file characteristics for several Archive Sets will result in ambiguous set membership. These situations are resolved in the following manner: 1. The Archive Set with the earliest definition in the command file is chosen. 2. Local definitions for the file system are chosen before the global definitions. These rules imply that more restrictive Archive Set definitions should be closer to the beginning of the command file. It is also possible to use the same Archive Set name for several different file characteristics. An example would assign files that are owned by several users into a single Archive Set. Assigning files to a special archive set called no_archive prevents files from being archived. This can be useful for temporary files. The no_archive archive set assignment definition must be a local definition to be effective. The Archive Set assignments may be followed by Archive Copy definitions. You can specify one or more of the following file characteristics: -user uname Include files belonging to user uname. -group gname Include files belonging to group gname. -minsize size Include files greater than or equal to size. size may be specified with the suffices 'b', 'k', 'M', 'G', and 'T', for bytes, kilobytes, megabytes, gigabytes, and terabytes. -maxsize size Include files less than size. -name regular_expression Include files with full paths that match regular_expression. The regular expression is limited to 255 characters. -access age Include files whose access time is older than age. The age may be specified with the suffixes 's', 'm', 'h', 'd', 'w' and 'y', for seconds, minutes, hours, days, weeks and years. -nftv By default, the access and modification times of files are validated to assure that these times are greater than or equal to the file creation time, and less than or equal to the time at which the file is examined. This is to provide proper archiving and unarchiving. For files that have been "migrated" into a directory, this may not be the desired behavior. The -nftv (no file time validation) parameter may be used to prevent the validation of file access and modification times for files that are in the archive set defined by these definitions. -after date_time Include files that have been created or modified since date_time. date_time is in the form "YYYY-MM- DD[Thh:mm:ss][Z]" (ISO 8601 format). If the time portion is not specified, 'Thh:mm:ss' missing, it is assumed to be 00:00:00. If the 'Z' is present, date_time is UTC, otherwise it is local. Examples: 2005-10-08T12:15:47 2005-10-08 2005-10-08T17:15:47Z Example: When controlling archiving for a specific file system (using the fs = fsname directive), directives local to the file system level are evaluated before the global directives. Thus, files may be assigned to a local archive set (including the no_archive archive set) instead of being assigned to a global archive set. This has implications when setting global archive set assignments such as no_archive. Assume, for example, the following archiver.cmd segment: no_archive . -name .*\.o$ fs = samfs1 allfiles . 1 10s fs = samfs2 allfiles . 1 10s At first look it appears that the administrator intended not to archive any of the .o files in both file systems. However, since the local archive set assignment allfiles is evaluated prior to the global archive set assignment no_archive, the .o files in in both file systems are archived. To ensure that no .o files are archived, the following segment would be used: fs = samfs1 no_archive . -name .*\.o$ allfiles . 1 10s fs = samfs2 no_archive . -name .*\.o$ allfiles . 1 10s SETTING FILE ATTRIBUTES The following directives are available to set file attributes: -release attributes Set the release attributes (see release(1)) for all files matching the file characteristics on this Archive Set definition. attributes may be any of 'a' always, 'd' reset to default, 'n' never, 'p' partial or 'sxx' partial size 'xx'. -stage attributes Set the stage attributes (see stage(1)) for all files matching the file characteristics on this Archive Set definition. attributes may be any of 'a' associative, 'd' reset to default, or 'n' never. ARCHIVE COPY DEFINITIONS SECTION The Archive Copy definitions determine when the archive copies are made for the files matching file characteristics. These definitions consist of lines beginning with a digit. This digit is the copy number. The first fields after the copy number are the option flags as described below: -release This causes the cache disk space for the files to be released immediately after the copy is made. -norelease This flag may be used to prevent automatic release of cache disk space until all copies marked with this flag are made. The -norelease option makes the archiver set eligible to be released after all copies have been archived, but the files will not be released until the releaser is invoked and selects them as release candidates. Using this flag on just one copy will have no effect on automatic release. The combination of -release and -norelease will cause the archiver to release the file when all the copies having this combination are made. With this usage, the archive set is released immediately, rather than waiting for the releaser to be invoked, as is the case with the -norelease option alone. If the -release option is used on a copy that does not have the -norelease option set, the file will get released when that copy is made, overriding the effect of any -norelease usage on other copies. The next field is the Archive Age of the file when the archive copy is made. The age may be specified with the suffixes 's', 'm', 'h', 'd', 'w' and 'y', for seconds, minutes, hours, days, weeks and years. The default Archive Age is 4 minutes. The next field is the Archive Age of the file when the copy is unarchived. The default is to never unarchive the copy. ARCHIVE SET COPY PARAMETERS SECTION Archive Set parameters may be set after all Archive Sets are defined. The beginning of this section is noted by the directive params. The section is ended by the end of the archiver command file or the directive endparams. Setting an archive set parameter requires at least three fields: the Archive Set Copy, the parameter name and the parameter value. The Archive Set Copy is the Archive Set name and copy number separated by '.'. Parameters may be set for all archive sets by using the pseudo Archive Set Copy allsets for the directive. If the allsets is specified without a copy number, the parameters apply to all Archive Set Copies. If specified with a copy number, the parameters apply to only those Archive Set Copies with the same copy number. All allsets directives must occur before those for any actual Archive Set Copies. Note: All parameter default values are 0 or none unless otherwise specified. Example: allsets -sort path allsets.1 -drives 3 allsets.2 -drives 2 All Archive Set Copies are assigned the -sort path parameter. All Archive Set Copy 1 will use 3 drives. All Archive Set Copy 2 will use 2 drives. If an archive copy of a file is being rearchived, an internal Archive Set Copy is used for scheduling the archive operation. It is called a Rearchive Set Copy, and uses the archive parameters from the actual Archive Set Copy. If desired, the Archive Set parameters may be set using the Archive Set Copy name followed by the character 'R'. The Rearchive Set Copy allows the users to differentiate 'new' and rearchive operations, and use different parameters for each operation. Example: archset.2 -drives 3 archset.2R -drives 1 -priority -1000 All 'new' archive copies are written using up to 3 drives. Rearchive copies are limited to 1 drive, and have a lower priority than the 'new' copies. In addition, the allsets.copy forms may be used. (For example, allsets.copyR) Archive Set Copy Parameters - General The general archive set copy parameters are as follows: -archmax target_size Set the Archive File maximum size for this Archive Set to target_size. Files to be archived will be placed on the media in a single Archive File of length less than or equal to target_size. If a single file is greater than target_size, then this restriction does not apply. If not specified, the archmax value for the media is used. -bufsize = buffer_size Set the archive buffer size to buffer_size * dev_blksize. The default buffer_size is 4. Valid values are 2 through 1024. If not specified, the default buffer size value for the media is used. This directive can also be specified as a global directive. For more information on specifying an archive buffer size, see the bufsize = media buffer_size [lock] directive described on this man page in the GENERAL DIRECTIVES section. -directio state Set the file reading method for archival. state may be "on" or "off". The reading performance of files for archival can be changed by using this parameter. If users are not reading files at the same time that they are being archived, then selecting on allows the archiver to read the file without using the system buffer cache and using pages that users might need. In the event that users are reading files while they are being archived, then off may be a better choice because the system buffer cache will provide data to the user and the archiver. The default is on. -disk_archive diskvol(Obsolete) Defines a disk archive set. This parameter is obsolete. Disk archive sets should be defined in the VSN associations or VSN pool definitions section. For more information on disk archiving, see the Sun StorEdge SAM Storage and Archive Management Guide. All of the other Archive Set parameters work with disk archiving except: -fillvsns, -ovflmin minimum_size, - reserve method, -tapenonstop. None of these cause an error if applied to an Archive Set that is assigned to disk archiving. -drivemax max_size Set the multiple drives maximum size for this Archive Set to max_size. When the -drives parameter is selected, the amount of data selected to be archived to each drive will be limited to max_size. Using this parameter can result in better drive utilization, because drives can take different amounts of time to archive files. The default is to not have this parameter set. -drivemin min_size Set the multiple drives minimum size for this Archive Set to min_size. When the -drives parameter is selected, multiple drives will be used only if more than min_size data is to be archived at once. The number of drives to be used in parallel will be the lesser of total_size / min_size and the number of drives specified by -drives. The default value is archmax. -drives number Set the maximum number of drives to use when writing the archive images for this Archive Set Copy to removable media. Segments are striped across the specified number of drives. The segments are separated into number archive files. Example: set_name.3 -drives 3 Allows the archiver to use up to 3 drives for archiving files in the archive set named set_name.3. If not specified, one drive will be used. -fillvsns The default action of the archiver is to utilize all volumes associated with an Archive Set for archiving. When a group of files is to be archived at the same time, a volume with enough space for all the files will be selected for use. This action may cause volumes to not be filled to capacity. Selecting this parameter causes the archiver to attempt to fill volumes by separating the group of files into smaller groups. -join method Organize the files in this Archive Set Copy so that each Archive tar File contains only files that match according to method. For selecting the desired organization, method may be: none Organize the Archive tar File so that the size of the Archive tar File is less than archmax. If the size of a single file is greater than archmax, it will be the only file in the Archive tar File. path Organize the Archive tar File so that the files included all have the same directory paths. Note: The use of -join path writes all data files to the same archive tar file. Therefore, many directories with a few small files creates many archive tar files. These small archive files can affect the performance of high speed tape drives. Also, -join path places all files from the same directory on a single volume. It is possible that a group of files might not fit on any available volume, including an empty volume. In such a case, files are never archived. For most applications, using the -sort path directive is more efficient than using the -join path directive, if the more restrictive operation of -join path is not a requirement. -lock Lock the archive copy buffer for the duration of the sam-arcopy(1M) operation. The -lock directive is effective only if direct I/O is enabled for the file being archived. If not specified, the file system controls the locks on the archive copy buffer. By default, this directive is disabled. This directive can also be specified as a global directive. For more information on controlling the archive buffer locks, see the bufsize = media buffer_size [lock] directive described on this man page in the GENERAL DIRECTIVES section. -offline_copy method This parameter specifies the method to be used for archiving files that are offline at the time archival is to be made. For selecting the desired offline file archiving method, method may be: none Files are staged as needed for each archive tar file before copying to the archive volume. direct Direct copy. Copy files directly from the offline volume to the archive volume without using the cache. Source volume and destination volume are different and two drives are available. For best performance in this mode, you should increase the file system mount parameter "stage_n_window" from its default of 256k. stageahead Stage the next archive tar file while the current archive tar file is written to the destination. With this method, one archive tar file is created on one tape drive (or disk archive) while the offline files needed to create the next archive tar file are being staged from another tape drive (or disk archive). Two drives are available and room is available on cache for all files in one archive tar file. stageall Stage all files before archiving. Use only one drive, and room is available on cache for all files. -ovflmin minimum_size Set the minimum size of a file that will require more than one volume in this Archive Set to minimum_size. Files to be archived that are smaller than this size will be placed on only a single volume of the media. Files that are this size or larger will be allowed to overflow one volume to at least one additional volume. If not specified, the ovflmin value for the media will be used. -rearch_stage_copy copy_number Use copy_number for staging an offline copy when rearchiving the copy defined by the Archive Set. By default, the file will be staged from the copy being rearchived. This option can be used if the copy being rearchived is not available or copy_number is located on a faster media. -reserve [ set | dir | user | group | fs ] This parameter specifies that the volumes used for archiving files in this Archive Set are "reserved". If this option is not used, Archive Sets are mixed on the media specified. This option specifies that each archive set has unique volumes. A so-called "ReserveName" is assigned to volumes as they are selected for use by the Archive Set. The ReserveName has three components: Archive Set, Owner, and file system. The keyword set activates the Archive Set. The keyword fs activates the file system component. The keywords dir, user, and group activate the Owner component. These three are mutually exclusive. The Owner component is defined by the file being archived. The dir keyword uses the directory path component immediately following the path specification of the Archive Set description. The user keyword selects the user name associated with the file. The group keyword selects the group name associated with the file. -rsort method -sort method Files in the Archive Set may be sorted according to method before being archived. The effect of the sort is keep files together according to the property associated with the method. If no method is specified, no sorting is performed. If -rsort is used, the sort is performed reversing the order specified by method. For selecting the sort, method can be one of the following: age Sort each Archive File by ascending modification time. The oldest files are archived first. none No sorting of the Archive File is performed. Files are archived in the order encountered on the file system. path Sort each Archive File by the full pathname of the file. This method will keep files in the same directories together on the archive media. priority Sort each Archive File by descending archive priority. The higher priority files are archived first. size Sort each Archive File by ascending file size. The smallest files are archived first. The largest files are archived last. -tapenonstop When files are archived to tape, the default writing mechanism closes the removable media tape file in between each Archive File. This action causes the tape subsystem to write a TapeMark followed by an EOF1 label and two TapeMarks. Before another Archive File can be written, the tape must be positioned backwards over the EOF1 label. Using the tapenonstop parameter causes the archiver to not close the removable media tape file between each Archive File, and write a Tape Mark to separate the Archive Files. This speeds writing Archive Files to tape. The tape cannot be unloaded in between Archive Files. Archive Set Copy Parameters - Priority The following parameters allow you to configure a priority system for archiving files. In the following priority parameters, the values are floating-point numbers such that -3.400000000E+38 < value < 3.402823466E+38. -priority age value Set the "Archive Age" property multiplier for files in this Archive Set to value. -priority archive_immediate value Set the "Archive immediate" property multiplier for files in this Archive Set to value. -priority archive_overflow value Set the "Multiple archive volumes" property multiplier for files in this Archive Set to value. -priority archive_loaded value Set the "Archive volume loaded" property multiplier for files in this Archive Set to value. -priority copy1 value Set the "Copy 1" property multiplier for files in this Archive Set to value. -priority copy2 value Set the "Copy 2" property multiplier for files in this Archive Set to value. -priority copy3 value Set the "Copy 3" property multiplier for files in this Archive Set to value. -priority copy4 value Set the "Copy 4" property multiplier for files in this Archive Set to value. -priority copies value Set the "Copies made" property multiplier for files in this Archive Set to value. -priority offline value Set the "File off line" property multiplier for files in this Archive Set to value. -priority queuewait value Set the "Queue wait" property multiplier for files in this Archive Set to value. -priority rearchive value Set the "Rearchive" property multiplier for files in this Archive Set to value. -priority reqrelease value Set the "Required for release" property multiplier for files in this Archive Set to value. -priority size value Set the "File size" property multiplier for files in this Archive Set to value. -priority stage_loaded value Set the "Stage volume loaded" property multiplier for files in this Archive Set to value. -priority stage_overflow value Set the "Multiple stage volumes" property multiplier for files in this Archive Set to value. Archive Set Copy Parameters - Scheduling As files are identified to be archived, they are placed in a list known as an Archive Request. The Archive Request is scheduled for archival at the end of a file system scan. The following archive set parameters control the archiving workload and assure timely archival of files: -queue_time_limit time Set the schedule queue time limit for the Archive Request to time. At the end of the time limit, a notification message will be sent once to alert monitoring entities that the ArchReq has been in the schedule queue longer than the time limit. -startage time Set the interval between the first file to be archived in the Archive Request and the start of archiving to time. This allows time to accumulate archival work after the first file has been scheduled for archival. -startcount count Set the start archiving file count to count. When count files have been identified for archival in the Archive Request, the archival operation begins. The default is to not set the count. -startsize size Set the minimum total size of all files to be archived after the first file to be archived in the Archive Request to size (in bytes). This allows the accumulation of archival work to be based on the total size of the files that have been scheduled for archival. The default is to not set the size. If more than one of -startage, -startcount, or -startsize are specified, the first condition encountered starts the archival operation. If neither -startage, -startcount, nor -startsize are specified, the archive request is scheduled based on the examine=method directive, as follows: o If examine = scan | scaninodes | scandirs, the archive request is scheduled for archiving after the file system scan. Note that examine = noscan is the default. o If examine = noscan, the default values are as follows: startage 10 minutes startcount 10,000 startsize 10 Gb The -startage, -startcount, and -startsize directives optimize archive timeliness versus archive work done. These values override the examine=method specification, if any. Example 1. If it takes an hour to create files for an Archive Set that uses -join path, then you can specify -startage 1h ensure that all files are created before scheduling the Archive Request. Example 2. You can specify -startsize 150G to direct the archiver to wait until 150 gigabytes of data are ready to be archived in an Archive Set. Example 3. If you know that 3000 files will be generated for archival, then specify -startcount 3000 to ensure that the files get archived together. Archive Set Copy Parameters - Recycling The following archive set parameters control recycling by archive set. If none of the following parameters are set for an archive set and the name of the archive set is not specified on the recycler's command line, the archive set will not be recycled. Volumes which comprise that archive set (unless also assigned to other archive sets) could be recycled as part of recycling the library which contains them. -recycle_dataquantity size This option sets a limit of size bytes on the amount of data the recycler will schedule for rearchiving so as to clear volumes of useful data. Note that the actual number of volumes selected for recycling may also be dependant on the -recycle_vsncount parameter. The default is 1 gigabyte (1G). -recycle_hwm percent This option sets the high water mark (hwm) for the archive set. The hwm is expressed as a percentage of the total capacity of the volumes associated with the archive set. When the utilization of those volumes exceeds percent, the recycler will begin to recycle the archive set. The default is 95%. This option is ignored for disk media recycling. -recycle_ignore This option inhibits the recycler from recycling this archive set. All recycling processing occurs as usual, except any media selected to recycle are not marked "recycle". This allows the recycler's choice of media to recycle to be observed, without actually recycling any media. -recycle_mailaddr mail-address This option specifies an email address to which informational messages should be sent when this archive set is recycled. The default is not to send any mail. -recycle_mingain percent This option limits selection of volumes for recycling to those which would increase their free space by percent or more. Volumes not meeting the mingain parameter are not recycled. The default is 50%. -recycle_vsncount count This option sets a limit of count on the number of volumes the recycler will schedule for rearchiving so as to clear volumes of useful data. Note that the actual number of volumes selected for recycling may also be dependant on the -recycle_dataquantity parameter. The default is 1. This option is ignored for disk media recycling. -recycle_minobs percent This option is used to set a threshold for the recycler's rearchiving process. When the percentage of obsolete files within an archived tar file on the disk reaches this threshold, the recycler begins moving the valid files from the archive into a new tar file. Once all of the valid files have been moved, the original tar file is marked as a candidate to be removed from the disk archive. This option is ignored for removable media recycling. The default is 50%. -unarchage time_ref Set the Unarchive Age computation time reference for this archive set to time_ref. The age of the files will be computed for unarchiving a copy from this time reference. For selecting the desired time reference, time_ref may be: access The age of files for unarchiving a copy is computed from the access time of the file. modify The age of files for unarchiving a copy is computed from the modification time of the file. The default time_ref is access. VSN POOL DEFINITIONS SECTION Collections of volumes may be defined in this section. The beginning of the section is noted by the directive vsnpools. The section is ended by the end of the archiver command file or the directive endvsnpools. A VSN pool definition requires at least three fields: the pool name, the media type, and at least one VSN. The media type is the two character mnemonic as described in the mcf(4) man page. The dk or cb identifiers can be used to define a disk archive set. For more information on disk archiving, see the Sun StorEdge SAM Storage and Archive Management Guide. VSNs are regular expressions as defined in regcmp(3C). VSN ASSOCIATIONS SECTION VSN associations are defined after all archive sets are defined. The beginning of the section is noted by the directive vsns. The section is ended by the end of the archiver command file or the directive endvsns. A VSN association requires at least three fields: the Archive Set Copy, the media type, and at least one VSN. The Archive Set Copy is the Archive Set name and copy number separated by '.'. VSN associations may be set for all archive sets by using the pseudo Archive Set Copy allsets for the directive. If the allsets is specified without a copy number, the VSNs apply to all Archive Set Copies. If specified with a copy number, the VSNs apply to only those Archive Set Copies with the same copy number. All allsets directives must occur before those for any actual Archive Set Copies. If an archive copy of a file is being rearchived, the Rearchive Set Copy uses the VSN associations from the actual Archive Set Copy. If desired, the VSN associations may be set using the Archive Set Copy name followed by the character 'R'. The Rearchive Set Copy allows the users to differentiate 'new' and rearchive operations, and use different VSNs for each operation. The media type is the two character mnemonic as described in the mcf(4) man page. VSNs are regular expressions as defined in regcmp(3C). or VSN pool denoted by the option name -pool vsn_pool_name Each VSN on a vsns line is used without leading or trailing spaces as input to regcmp(3C). The compiled form is saved with the Archive Set Copy definition. When a volume is needed for an Archive Set Copy, each VSN of each library or manual drive that has sufficient space and is allowed to be used for archives, is used as the "subject" argument to regex(3C). The archive set copy vsn expressions are used as the "re" argument to regex(3C). If regex(3C) returns with a successful match, the volume is used for the archive set copy. Example: set_name.3 mo optic.* Assigns all files in set_name.3 to the mo media with VSNs beginning with optic. VSN associations may be defined for all archive sets by using the pseudo Archive Set Copy allsets for the directive. If the allsets is specified without a copy number, the VSN associations apply to all Archive Set Copies. If specified with a copy number, the VSN associations apply to only those Archive Set Copies with the same copy number. All allsets directives must occur before those for any actual Archive Set Copies. SEE ALSO release(1), stage(1). archiver(1M), archiver.sh(1M), sam-archiverd(1M), sam- arcopy(1M), sam-arfind(1M), sam-recycler(1M). regcmp(3C). diskvols.conf(4), mcf(4). Sun Microsystems Last change: 13 Aug 2007 File Formats defaults.conf(4) NAME defaults.conf - Set default values for Sun StorEdge QFS and Sun StorEdge SAM software SYNOPSIS /etc/opt/SUNWsamfs/defaults.conf AVAILABILITY SUNWqfs SUNWsamfs DESCRIPTION The defaults configuration file allows the site to set certain default values within the Sun StorEdge QFS and Sun StorEdge SAM environments. The defaults.conf file is read when sam-fsd is started. It may be changed at any time while sam-fsd is running. The changes will take place when sam-fsd is restarted, or sent the signal SIGHUP. Temporary changes to the environment values can be made using the samset(1M) command. The defaults.conf file consists of directive lines that are separated into two sections, the environment variable section and the trace file control section. Environment variables. The commands for the environment section of the file consists of a list of keyword = value pairs that set site-definable defaults. All keyword and value entries are case-sensitive and must be entered as shown. Values can be either unquoted strings (if string values are expected) or integers in decimal (123), octal, (0123) or hex (0x123) format. The keywords and their expected arguments are as follows: attended = yes | no If attended = yes, it is assumed that an operator is available to mount media that is not flagged as unavailable by the historian; the default is yes. If attended = no, any request for media known to the historian is rejected unless it is already mounted. debug = options Sets the default for the debug flags used by the Sun StorEdge QFS and Sun StorEdge SAM daemons for logging messages. For options, specify a space-separated list of debug options from the list of possible options described on the samset(1M) man page. The default is logging. devlog = eq_ord [ event ... ] Manipulates the device log event flags for the device specified by Equipment Ordinal eq_ord. The eq_ord must be either the keyword all (to specify all devices) or must match an Equipment Ordinal from the mcf file. The device log event flags control the events that get written to the device log files. For the list of possible event arguments, see the samset(1M) man page. To specify more than one event, separate the events in the list with space characters. The default is err retry syserr date. dev_blksize = size Specifies the default block size for tapes of type dev. For size, specify 16, 32, 64, 128, 256, 512, 1024, or 2048. The size value is multiplied by 1024 to arrive at the actual block size. For information on supported dev arguments and for information on the default released block sizes for various media, see the mcf(4) man page. The default is used when no size is specified or during automatic labeling when labels = barcodes has been specified. For information on how the default can be overridden when manually labeling a tape, see the tplabel(1M) man page. dev_delay = seconds Specifies the dismount time, in seconds, for device type dev. After a cartridge is loaded onto this device type, this time must elapse before the cartridge unloaded and another cartridge is loaded. By default, dev_delay = 30. For information on supported dev arguments, see the mcf(4) man page. dev_position_timeout = seconds Specifies the timeout value, in seconds, to be used during tape positioning for device type dev. During most tape positioning command processing (such as locate and space) this is the maximum amount of time to wait for the command to complete. For information on the default values, see the example file (/opt/SUNWsamfs/examples/defaults.conf) supplied with your software. Any device not in the example file defaults to 1800 seconds. For information on supported dev arguments, see the mcf(4) man page. dev_unload = seconds Specifies the unload wait time, in seconds, for device type dev. This is the amount of time that the library daemons wait after the device driver returns from a SCSI unload command. This interval gives the library time to eject the media, open the door, and perform other actions before the daemon commands the library to remove the media. The seconds specified should the longest time needed for the worst-case library configured. For information on the default values, see the example file (/opt/SUNWsamfs/examples/defaults.conf) supplied with your software. Any device not in the example file defaults to 0 seconds. For information on supported dev arguments, see the mcf(4) man page. dio_min_file_size = size Stages files larger size megabytes with direct I/O. For size, enter an integer number such that 0 < size < 2147483647 megabytes. If size = 0, paged I/O is used to stage all files. The default size is 100 megabytes. exported_media = value Declares exported media to be available or unavailable to the historian, as follows: o If exported_media = available, media exported from a library is considered to be available in the historian. The default is available. o If exported_media = unavailable, media exported from a library is considered to be unavailable in the historian. Cartridges with this characteristic are not used by the archiver, stager, or other Sun StorEdge SAM-FS tools. They are considered to reside outside of the Sun StorEdge SAM-FS environment. This might be used, for example, for cartridges to be transported to offsite storage. For more information, see the historian(7) man page. idle_unload = seconds Specifies the time, in seconds, that a library-controlled device can be idle before the media in that device is unloaded. Specifying idle_unload = 0 disables this feature. By default, idle_unload = 600, which is 10 minutes. shared_unload = seconds Specifies the time, in seconds, that a shared library-controlled device can be idle before the media in that device is unloaded. A device is shared if it is used by more than one Sun StorEdge SAM server. For more information on shared devices see the sony(7), the ibm3494(7), or the stk(7) man page. Specifying shared_unload = 0 disables this feature. By default, shared_unload = 60, which is 60 seconds. inodes This keyword is still accepted for backward compatibility, but it has no effect. For more information, see the samfs.cmd(4) man page. labels = mode For tape libraries with bar code label readers, this keyword sets the tape label equal to the first or the last characters of the bar code label (uppercased). For mode, specify either barcodes, barcodes_low, or read, as follows: o If labels = barcodes, the first part of the bar code is used as the label. Default. o If labels = barcodes_low, the last part of bar code is used as the label. o If labels = read, the label is read from the tape. If you wish to have the labels different from the barcodes on a library with a bar code label reader, you must set labels = read. When labels is set to barcodes or barcodes_low, a label is written to the tape before the write is enabled for any tape mounted for a write operation that is write enabled, unlabeled and has a readable bar code label. log = facility Sets the facility code used for issuing log messages. For information on the accepted facility types, see the syslog(3) man page. The default is LOG_LOCAL7. oper_privileges = privilege Adds privileges to the operator group. By default, members of the operator group do not have the privileges to perform the following tasks: media labeling, performing storage element movement actions, submitting full audit requests, changing a device state (except to ON a device), and clearing mount requests. To grant the privileges needed to perform those actions, specify one or more of the following privilege arguments. privilege Result all Grants all privileges in this list. clear Grants the ability to clear cartridge load requests. fullaudit Grants the ability to perform a full library audit. label Allows cartridge labeling. slot Allows mounting, unloading, and moving cartridges within a library. state Grants the ability to change the device state. Operator group members can ON devices regardless of this setting. Use a space character between privilege arguments if specifying more than one. operator = group Specifies the name of the group that to be granted operational privileges within certain commands (chmed(1M), load(1M), samfsdump(1M), and samfsrestore(1M)) and command queues. Only one group name can be specified. Users must have their effective group IDs set to group in order to gain operational privileges. optical = media_type Sets the default media type to media_type when a generic optical disk (od) is requested. A string value is expected. For information on the accepted media types, see the mcf(4) man page. The default is mo. previews = requests Sets the number of outstanding mount requests. Care should be taken when changing this value. Each entry takes about 500 bytes of shared memory. By default, previews = 100. samrpc = on | off Invokes the RPC API server process. If samrpc = on, the RPC API server process, sam-rpcd, is automatically started when Sun StorEdge SAM-FS or Sun StorEdge QFS is started. By default, samrpc = off, so sam-rpcd is not started automatically. alerts = on | off Specifies whether alert notification via Simple Network Management Protocol (SNMP) or fault history logging via the GUI is supported. With this turned on, you can monitor a Sun StorEdge QFS or Sun StorEdge SAM system remotely from a management console such as Sun Remote Services (SRS) By default, alerts=on is in effect. stale_time = minutes Sends an error to any request for removable media that has waited for minutes number of minutes. Setting stale_time = 0, disables this function. By default, stale_time = 30. tape = media_type Sets the default media type to media_type when a generic tape (tp) is requested. A string value is expected. For information on the accepted media types, see the mcf(4) man page. The default is lt. timeout = seconds Sets the timeout interval, in seconds, for direct access removable media. If a process fails to issue an I/O request to the device within this time, the device is removed from job assignment and the process receives an ETIME when the next I/O to the device commences. Specifying timeout = 0 disables this timeout. The minimum value allowed is timeout = 600. For backwards compatibility, values from 1 to 599 are allowed, but are overridden by the minimum value. By default, timeout = 600. tp_mode = mode Specifies the mode set for tape drive device nodes when not under control of the Sun StorEdge SAM software. For information, see the chmod(2) man page. When the Sun StorEdge SAM software is controlling the drive, the mode bits are 0660. tapealert = eq_ord on | off Enables or disables media changer or tape drive TapeAlert support by Equipment Ordinal eq_ord. The eq_ord must be either the keyword all (to specify all devices) or must match a tape device Equipment Ordinal from the mcf file. By default, tapealert = all on. samstorade = on | off Enables or disables the StorADE API. The API provides Sun StorEdge SAM device attributes and health information for StorADE fault analysis. By default, samstorade = on. sef = eq_ord [on|off|default] interval Enables or disables support for tape drive implemented Log Sense delivered via sysevents by Equipment Ordinal eq_ord. The eq_ord must be either the keyword all (to specify all devices) or must match an Equipment Ordinal from the mcf file. The interval specfies the log sense polling rate. A value of 300 is a polling interval once every five minutes. A string value of "once" specifies one time just before media unload and is the default. A value of 3600 is a polling interval once every hour. The smallest polling interval is five minutes. By default, sef = all on once. Note: The defaults.conf sef entry only controls the equipment number and frequency interval for sef data. It is the presence or absence of the file /var/opt/SUNWsamfs/sef/sefdata at SAM-QFS initialization that determines if sef will run or not. When /var/opt/SUNWsamfs/sef/sefdata is present, sef will be initialized. You must create the sefdata file yourself. To turn off sef, the sefdata file must be removed or renamed. tapeclean = eq_ord autoclean [on|off] logsense [on|off] Enable or disable the robot initiated auto- cleaning feature. Enable or disable additional auto-cleaning log sense cleaning indicators from the TapeAlert log sense page(2E) flags clean now(20), clean periodic(21) and expired cleaning media(23) and the Sequential-Access Device log sense page(0C) cleaning required flag in parameter(256). Support is by Equipment Ordinal eq_ord. The eq_ord must be either the keyword all (to specify all devices) or must match a tape device Equipment Ordinal from the mcf file. Note that the logsense on setting has no effect unless autoclean is also on. By default, tapeclean = all autoclean off logsense on. Note: When using the auto-cleaning feature with a library that has more than two drives, it is recommended that you have at least two cleaning cartridges per robot. If a cleaning cartridge is not available when a drive needs to be cleaned, the drive will be put into a down state. Trace file controls. The daemon trace files are controlled by directives in the trace file section. This section begins with the trace directive, and ends with the endtrace directive. The trace file control directives are of the form: daemon_name.variable_name = value daemon_name = on daemon_name = off daemon_name can be one of the following: sam-archiverd, sam-catserverd, sam-fsd, sam-rftd, sam-recycler, sam- sharefsd, sam-stagerd, sam-serverd, sam-clientd, fsmgmt, or all . Note that fsmgmt is used by fsmgmtd and libfsmgmt.so. If daemon_name is all, then the variable_name is set to value for all daemons. For the form: daemon_name = on the trace file controls will be set to the pre-defined values for daemon_name. In particular, using only the directive all = on enables tracing for all daemons. The trace files are written to files named for the daemons (e.g. sam-rftd) in the /var/opt/SUNWsamfs/trace subdirectory. For the form: daemon_name = off tracing will be turned off for daemon_name. The variable_name is one of: file, options, age, or size. daemon_name.file file_name set the name of the trace file to file_name. The default is no trace file. If the daemon_name is all, then file_name is the name of the trace subdirectory that will contain the daemon tracefiles. file_name must be absolute in this case. The default subdirectory is /var/opt/SUNWsamfs/trace. If file_name is relative (no leading '/'), the file name will be made relative to the trace base directory. If the file does not exist, sam-fsd will create it. daemon_name.options = option_list Set the trace file options to option_list. option_list is a space separated list of trace options. A trace option is an event to trace, or an element to include in the trace line. To exclude an option, prefix the option with a '-'. For selecting events, option may be one or more of: none Clear all event types. all Set event types for tracing the most interesting events. These are: cust err fatal ipc misc proc rft. alloc Memory allocations. cust Customer notification syslog or notify file messages. err Non-fatal program errors. fatal Fatal syslog messages. files File actions. rft File transfer events. ipc Inter process communication. misc Miscellaneous. oprmsg Operator messages. proc Process initiation and completion. queue Archiver queue contents when changed. For selecting message elements, option may be one or more of: date Include the date in message (the time is always included). module Include source file name and line number in message. type Include event type in message. The pre-defined events are: cust, err, fatal, misc, proc, rft. The message elements program[pid] and time are always included and can't be deselected. daemon_name.age = age Set the time between trace file rotations to age. age may be specified with the seconds, minutes, hours, days, weeks and years. Note: Do not set this value to two minutes or less. If you do, the rotation will never take place. sam-fsd can perform trace file "rotations" using the script /opt/SUNWsamfs/sbin/trace_rotate. Trace file rotations are useful to control the size of trace files. daemon_name.size = size Set the trace file size at which trace file rotations will be performed. size may be specified with the suffices 'b', 'k', 'M', 'G', and 'T', for bytes, kilobytes, megabytes, gigabytes, and terabytes. EXAMPLES Here is a sample defaults.conf configuration file. optical = mo debug = logging debug timing tape = lt log = LOG_LOCAL7 timeout = 30 idle_unload = 600 tp_mode = 0666 rc_delay = 10 cy_delay = 10 ml_delay = 10 hp_delay = 10 ds_delay = 10 lt_unload = 7 st_unload = 15 lt_blksize = 16 operator = sam oper_privileges = label slot trace all = on # Turn on tracing for all daemons sam-archiverd.size = 10M # Rotate archiver trace file after 10 megabytes sam-rftd.file = /tmp/sam-rftd.trace # change file name for sam-rft daemon sam-recycler = off # Turn off tracing for sam-recycler daemon endtrace FILES /opt/SUNWsamfs/examples/defaults.conf Contains an example of a defaults.conf file. SEE ALSO request(1). samset(1M), sam-fsd(1M), tplabel(1M), tapealert(1M). chmod(2). syslog(3). mcf(4), samfs.cmd(4), trace_rotate(4), sefsysevent(4). historian(7). Sun Microsystems Last change: 29 Jun 2005 File Formats devlog(4) NAME devlog - Device log file SYNOPSIS /var/opt/SUNWsamfs/devlog/nn AVAILABILITY SUNWsamfs DESCRIPTION In Sun StorEdge SAM-FS and Sun SAM-QFS environments, media or tape hardware events that require operator intervention (such as tape positioning errors and requests for cleaning) are logged to file in the following directory: /var/opt/SUNWsamfs Within the preceding directory, events are logged to files that are named for the devices listed in the mcf file. For example, file devlog/47 logs all events for the device identified by Equipment Ordinal 47 in the mcf file. After an event is logged, you can use the tapealert(1M) command to read the event logged in the devlog/nn file, interpret the event, and write it to a text file for easier viewing. For more information about the specific events logged to the device log files, see the tapealert(1M) man page. The tapealert(1M) command logs the following two types of messages in the device log (devlog/nn) file: o Device TapeAlert support o Active TapeAlert flags The preceding type of messages are the undecoded TapeAlert events. The tapealert(1M) command decodes these messages into a more readable format. The undecoded device log messages for device support contains the following information: Field Content 1 The date in year/month/day format. 2 The time expressed in a 24-hour clock. 3 The message number, followed by TapeAlert and supported. TapeAlert messages start at 12000. The following is an example of a device support message: 2003/06/13 10:52:23 12001 TapeAlert supported The device log messages for active TapeAlert flags contain the following information: Field Content 1 The date in year/month/day format. 2 The time expressed in a 24-hour clock. 3 The message number, followed by TapeAlert. TapeAlert messages start at 12000. 4 The characters eq= followed by the mcf(4) equipment ordinal number. 5 The characters type= followed by the inquiry peripheral device type. 6 The characters seq= followed by the sysevent sequence number. The sysevent sequence number is zero if the sysevent_post_event function fails or is not called. The sysevent event handler $sequence macro is the same as the devlog/nn file's seq=n number. 7 The characters len= followed by the number of valid TapeAlert flags. 8 The flags field. The 64 TapeAlert flags are written in big endian format. The most significant bit, on the left, is flag 64. The least significant bit is flag 1. The following is an example of a TapeAlert flags message: 2003/06/13 10:52:23 12006 TapeAlert eq=91 type=1 seq=8 len=50 flags=0x0002004000000000 A decoded TapeAlert flag consists of four parts: 1. Flag 2. Severity 3. Application message 4. Probable cause The T10 Technical Committee defines three types of flags. Table 1 lists these flags in order of increasing severity. Table 1. Flag Types Severity Urgent Intervention Risk of Data Loss Explanation Critical X X Warning X X Information X If an Information-level flag is issued, you can perceive it as a predicted failure. Take the time to correct the problem before it worsens. The tapealert(1M) command supports the minimum flag subset as defined by the T10 Committee. Table 2 shows these flags. Table 2. Tape Drive TapeAlert Flags - Minimum Subset Flag Number, Type Explanation 3h, Hard error Active for any unrecoverable read/write/positioning error. Internally deactivated when the media is unloaded. This flag is active as specified in flag number 5h and 6h. 4h, Media Active for any unrecoverable read/write/positioning error that is due to faulty media. Internally deactivated when the media is unloaded. 5h, Read failure Active for any unrecoverable read error where the diagnosis is uncertain and could either be faulty media or faulty drive hardware. Internally deactivated when the media is unloaded. 6h, Write failure Active for any unrecoverable write/positioning error where the diagnosis is uncertain and could either be faulty media or faulty drive hardware. Internally deactivated when the media is unloaded. 14h, Clean now Active when the tape drive detects a cleaning cycle is needed. Internally deactivated when the tape drive is successfully cleaned. 16h, Expired cleaning Active when the tape drive detects a cleaning cycle was attempted but was not successful. Internally deactivated when the next cleaning cycle is attempted. 1fh, Hardware B Active when the tape drive fails its internal Power-On-Self-Tests (POST). Not internally deactivated until the drive is powered off. Table 3 summarizes the errors in the devlog/nn file. Table 3. TapeAlert Flag Definition Groupings for Tape Drives With or Without an Autoloader Flag Number(s) Definition 01h to 13h Tape drive write/read management 14h to 19h Cleaning management 1Ah to 27h Tape drive hardware errors 28h to 31h Tape autoloader errors 32h to 40h Further tape errors The information in tables 1, 2, and 3 is derived from SCSI Stream Commands - 2 (SSC-2), Revision 08d. SEE ALSO tapealert(1M). mcf(4). Sun Microsystems Last change: 10 Dec 2003 File Formats diskvols.conf(4) NAME diskvols.conf - Defines disk archive volumes for Sun StorEdge SAM-FS or Sun SAM-QFS environments SYNOPSIS /etc/opt/SUNWsamfs/diskvols.conf AVAILABILITY SUNWsamfs DESCRIPTION A Sun StorEdge SAM-FS or Sun SAM-QFS file can have one or more of its archive copies written to a disk archive resource. A disk volume that represents the resource is stored in the inode of the archived file. The disk volume configuration file, diskvols.conf, defines the mapping between a disk volume and the corresponding resource. The sam-fsd daemon reads the diskvols.conf file when the sam-fsd daemon is started. The diskvols.conf file can be changed at any time while the sam-fsd daemon is running. The changes take effect when the sam-fsd daemon is restarted or sent the signal SIGHUP. The mappings are specified one per line. Each line consists of two fields separated by white space. Leading white space is ignored. Everything after a pound character (#) is ignored. Lines can be continued by using a backslash character (\) as the last character on the line. The syntax for this line is as follows: disk_volume resource where: disk_volume An alphanumeric string. The string can contain up to 31 characters. resource A resource specification in one of the following formats: pathname This format contains the path name of the disk archive directory on the local host. [host:]pathname This format specifies the host as the name of the disk archive server and pathname as the path name of the disk archive directory on that host. stk5800 host[:port] This format defines a disk volume as residing on a Sun StorageTek 5800 Storage System. The host field contains the name or IP address and port as the port number of the Sun StorageTek 5800 Storage System. By default, the port number is 8080. NOTE: Extreme care must be taken when configuring disk archiving in an environment with multiple SAM-QFS servers. The diskvols.conf file for each SAM-QFS server must point to a unique set of disk volume resource specifications (disk archiving target directories). If any of these are shared between different SAM-QFS servers, then running the recycler from one SAM-QFS server will destroy the disk archive data that is being managed by the other SAM-QFS server. CLIENT DEFINITIONS SECTION The clients and endclients directives delimit this section of the diskvols.conf file. The client definitions section defines the trusted client systems. After the disk archiving server accepts a client connection, it verifies that the socket address belongs to a host in the trusted client definitions section. If not, the connection is refused. EXAMPLES This example shows two diskvols.conf files. File 1 is a diskvols.conf file on client system earth that defines the following: o There is one volume serial name (VSN) for a local disk archive. o There are two remote VSNs. Remote VSN remote1 resides in /quidditch on the remote server gryffindor, and remote VSN remote2 resides in /quidditch on remote server ravenclaw. o There is one volume serial name (VSN) for a Sun StorageTek 5800 Storage System. # # This is file /etc/opt/SUNWsamfs/diskvols.conf on local system earth # local_archive /DiskArchive remote1 gryffindor:/quidditch remote2 ravenclaw:/quidditch stk_archive stk5800 mars File 2 is the diskvols.conf file that resides on the server system gryffindor and ravenclaw. Only the diskvols.conf file for server gryffindor is shown. # # This is file /etc/opt/SUNWsamfs/diskvols.conf on server system gryffindor # clients earth endclients SEE ALSO archiver(1M), sam-fsd(1M). archiver.cmd(4). WARNINGS If more than one SAM-FS environment is sharing a Sun StorageTek 5800 Storage System you must take extra care when configuring the diskvols.conf file. If you are running multiple connections to a Sun StorageTek 5800 Storage System disk archive, then the disk_volume name needs to be unique across all SAM-FS environments. For example, stk_archive_earth on one server, stk_archive_pluto on the next server, etc. # # This is file /etc/opt/SUNWsamfs/diskvols.conf on server earth # stk_archive_earth stk5800 mars # # This is file /etc/opt/SUNWsamfs/diskvols.conf on server pluto # stk_archive_pluto stk5800 mars It is important to follow this recommendation, because there is no enforcement of this restriction in the SAM-FS software. Sun Microsystems Last change: 07 Feb 2007 File Formats ftp.cmd(4) NAME ftp.cmd - Renamed to "rft.cmd" SEE ALSO rft.cmd(1M). Sun Microsystems Last change: 04 AUG 2003 File Formats hosts.fs(4) NAME hosts.fs - Host information for Sun StorEdge QFS shared file systems SYNOPSIS /etc/opt/SUNWsamfs/hosts.fs AVAILABILITY SUNWqfs SUNWsamfs DESCRIPTION The /etc/opt/SUNWsamfs/hosts.fs file specifies the hosts and network interfaces used by a Sun StorEdge QFS shared file system. The fs suffix must be the family set name of the Sun StorEdge QFS shared file system as specified in the mcf(4) file. The file /etc/opt/SUNWsamfs/hosts.fs is required by sammkfs(1M) at the time a Sun StorEdge QFS shared file system is created. The sammkfs(1M) command reads /etc/opt/SUNWsamfs/hosts.fs and integrates the information into the file system when initializing the file system. The file system's shared hosts information can be subsequently modified using the samsharefs(1M) command. Another file, hosts.fs.local(4), can also reside on each host system included in the shared file system. Daemons local to each host system use the shared hosts file and the local hosts file, if any, to initialize network connections for the shared file system. Each file system's shared hosts file determines the host configuration for that file system. This includes the following: o The identity of the file system's metadata server. o The host systems (and host IP interfaces) that are allowed to connect to the Sun StorEdge QFS shared file system's metadata server. o The identities of the potential metadata server hosts. These are systems that can act as the file system's metadata server if the preferred metadata server is unavailable. The hosts.fs file is comprised of lines containing five fields of information. Each line corresponds to one host that is permitted to access the file system. The fields are as follows: Field Number Content 1 The name of the host. The host name field contains the name of a host that is to be permitted access to the shared file system. The value of this field must match the output of the hostname(1) command on that host. 2 The host IP addresses. The host IP address field contains a list of one or more host IP interface addresses or names that the metadata server must be able to resolve to IP addresses. If there are multiple IP interfaces that a host can use to connect to a server, they must be separated by commas. You should avoid using a domain name in this field, because during the reboot process, when sam-fsd is trying to contact the metadata server, naming services are likely not up. This means that the name may not be resolvable if it is not in the /etc/inet/ipnodes or /etc/inet/hosts file; this will cause the mount to fail and could cause the reboot to hang. 3 The server priority of the host. The server priority field is a numeric field. If the field is zero, the host cannot act as the metadata server for the file system. If the field is nonzero, the host can act as the metadata server for the file system. 4 A number that indicates the stager priority. This numeric field is not used by the shared file system software. It is recommended that this field be set to zero. 5 A server field. This optional field must be set for one of the hosts in the hosts.fs file. That host must have a nonzero server priority field. If present, this field must contain the string server. In this file, a pound character (#) indicates a comment. Comments continue from the pound character to the end of the line. All characters to the right of the pound character are ignored. After the file system is initialized using the sammkfs(1M) command, only the metadata server host is permitted to run the samfsck(1M) to repair the file system. The server on which sammkfs(1M) is run is typically declared to be the metadata server. When a client is attempting to connect to the metadata server, the client obtains the list of names and addresses from the second field, which is the host IP address field, of the server's row in the hosts.fs file. It attempts to connect to these names, in the order in which they appear, until it connects successfully. If the client has a local hosts.fs.local(4) file, only the names or addresses that are present in both files are used. The hosts.fs.local(4) file determines the order in which host connections are attempted. When a metadata server receives a connect attempt, it performs address lookups on the values from the second column of the hosts.fs file until it finds one that matches the IP address of the incoming connection. If it fails to find one, it refuses the connection. For file systems that are mounted at boot time, you should add the file system's hosts to the /etc/inet/hosts or /etc/inet/ipnodes files. On clients, the names of the servers should be added; on servers, all of the file system's hosts should be added. EXAMPLES Example 1. The following is a sample hosts.fs configuration file called /etc/opt/SUNWsamfs/hosts.shsam1. # # shsam1 config, titan/tethys servers, mimas/dione clients # # This file goes in titan:/etc/opt/SUNWsamfs/hosts.shsam1, # and is used by 'sammkfs -S shsam1' to initialize the FS # meta data. Subsequent changes to the configuration are # made using samsharefs(1M). # # titan titan 1 0 server tethys tethys 2 0 mimas mimas 0 0 dione dione 0 0 Example 2. This hosts configuration file is more complicated that the one in example 1. It supports a configuration where two potential servers also have a private interconnect between them. # # shsam1 config, titan/tethys servers, mimas/dione clients # # This file goes in titan:/etc/opt/SUNWsamfs/hosts.shsam1, and # is used by mkfs -S to initialize the FS meta data. Subsequent # changes to the configuration are made using samsharefs(1M). # # titan titan-ge,titan.xyzco.com 1 0 server tethys tethys-ge,tethys.xyzco.com 2 0 mimas mimas.xyzco.com 0 0 dione dione.xyzco.com 0 0 To ensure that titan and tethys always connect to each other through their private interfaces, titan-ge and tethys-ge, each must have a hosts.shsam1.local file (see hosts.fs.local(4)). To avoid the inefficiencies of attempting to connect to the unreachable titan-ge and tethys-ge interfaces, mimas and dione should also have their own hosts.shsam1.local files. FILES /opt/SUNWsamfs/examples/hosts.shsam1 Contains an example of a hosts.fs file. /opt/SUNWsamfs/examples/hosts.shsam1.local.server /opt/SUNWsamfs/examples/hosts.shsam1.local.client Contain examples of hosts.fs.local(4) files. SEE ALSO hostname(1). samfsck(1M), samfsconfig(1M), sammkfs(1M), samsharefs(1M), sam-sharefsd(1M). hosts.fs.local(4), mcf(4). Sun Microsystems Last change: 29 Apr 2002 File Formats hosts.fs.local(4) NAME hosts.fs.local - Local host information for Sun StorEdge QFS shared file systems SYNOPSIS /etc/opt/SUNWsamfs/hosts.fs.local AVAILABILITY SUNWqfs SUNWsamfs DESCRIPTION A /etc/opt/SUNWsamfs/hosts.fs.local file can reside on each host system included in the Sun StorEdge QFS shared file system. This file is used in conjuntion with the shared hosts file, which resides in the shared file system and is initialized by sammkfs(1M) from hosts.fs(4), to initialize network connections between the hosts of a shared file system. For more information, see the hosts.fs(4) and samsharefs(1M) man pages. The Sun StorEdge QFS shared file system daemon uses the /etc/opt/SUNWsamfs/hosts.fs.local file and the shared hosts file present in the file system during initialization and reconfiguration to determine the server interfaces to which it should attempt to connect. Its function is to restrict the server interfaces to which each client connects. The fs portion of the name must be the family set name of the Sun StorEdge QFS shared file system as specified in the mcf file. For more information on the mcf file, see the mcf(4) man page. Each line in the hosts.fs.local file corresponds to a possible metadata server. Each line contains the following fields: Field Number Content 1 The name of the host. This field contains the name of a potential metadata server host to which the local host can connect. This field must match the first field of the host in the shared hosts file. You can use the samsharefs(1M) command to verify the content of the fields of the shared hosts file. 2 A comma-separated list of host IP names or addresses. This should be a subset of the second field from the same hosts entry in the shared hosts file. The hosts.fs.local file is typically generated by copying the shared file system's shared hosts file to /etc/opt/SUNWsamfs/hosts.fs.local on each host. Each line referring to a non-server host is then deleted, and the third through fifth fields in the remaining lines are deleted. The network topology of the hosts is then examined in conjunction with the file, and the server interfaces that the local host should not attempt to connect to are removed from the second field. When all of these have been removed, the file is written out. The samd(1M) command is then used to cause any configuration changes to take effect. During startup and file system reconfiguration, the sam- sharefsd(1M) daemon attempts to connect to the server host. To do this, it searches the shared hosts file for the server's identity, and it extracts the list of IP names and addresses from the server's shared hosts file entry. The daemon then looks up the server's name in the file system's local hosts file, if any. If a local hosts file does not exist, the daemon uses the list from the shared hosts file. If the local hosts file does exist, then the corresponding list of host addresses is found in the local hosts file, the two lists of host addresses are searched (lexically) for common entries, and a common list is generated. The ordering of the list is determined by the local hosts file (left-most first). The names or addresses in the common list are looked up and used to attempt to connect to the server. If an attempt fails, the daemon attempts using any remaining addresses in order until all the addresses have been tried. EXAMPLES The following shared hosts configuration file supports a configuration in which two potential servers share a private interconnection and communicate to the other hosts sharing the file system using a separate network. The examples in this section show the hosts.shsam1.local files that can be found on the various hosts. # # shsam1 config, titan/tethys servers, mimas/dione clients # # This file goes in titan:/etc/opt/SUNWsamfs/hosts.shsam1, and # is used by 'mkfs -S shsam1' to initialize the FS meta data. # Subsequent changes to the configuration are made using # samsharefs(1M). # titan titan-ge,titan.xyzco.com 1 0 server tethys tethys-ge,tethys.xyzco.com 2 0 mimas mimas.xyzco.com 0 0 dione dione.xyzco.com 0 0 To ensure that titan and tethys always connect to each other through their private interfaces, titan-ge and tethys-ge, each requires a hosts.fs.local(4) file. To achieve this, files titan:/etc/opt/SUNWsamfs/hosts.shsam1.local and tethys:/etc/opt/SUNWsamfs/hosts.shsam1.local would contain the following lines: # # shsam1 server local config, titan/tethys servers, mimas/dione clients # titan titan-ge tethys tethys-ge To avoid the delays and inefficiencies of having mimas and dione attempt to connect to titan and tethys through the inaccessible, private titan-ge and tethys-ge interfaces, mimas and dione should also have their own hosts.fs.local(4) files. Files mimas:/etc/opt/SUNWsamfs/hosts.shsam1.local and dione:/etc/opt/SUNWsamfs/hosts.shsam1.local contain the following lines: # # shsam1 client local config, titan/tethys servers, mimas/dione clients # titan titan.xyzco.com tethys tethys.xyzco.com FILES /opt/SUNWsamfs/examples/hosts.shsam1 Contains an example of a hosts.fs file. /opt/SUNWsamfs/examples/hosts.shsam1.local.server /opt/SUNWsamfs/examples/hosts.shsam1.local.client Contain examples of hosts.fs.local files. SEE ALSO samfsck(1M), samfsconfig(1M), sammkfs(1M), samsharefs(1M), sam-sharefsd(1M). hosts.fs(4), mcf(4). Sun Microsystems Last change: 29 Apr 2002 File Formats inquiry.conf(4) NAME inquiry.conf - SCSI inquiry strings for Sun StorEdge SAM-FS or Sun SAM-QFS device types SYNOPSIS /etc/opt/SUNWsamfs/inquiry.conf AVAILABILITY SUNWsamfs DESCRIPTION The inquiry configuration file, inquiry.conf, maps a SCSI device to a Sun StorEdge SAM-FS or Sun SAM-QFS device type. The inquiry.conf file contains the vendor identification and product identification reported by a SCSI device in response to an inquiry command. Entries in the file are made up of three quoted fields separated by a comma and/or white space and optionally followed by a comment. These entries have the following format: "vendor_id", "product_id", "SAM-FS_name" #comment The vendor_id and product_id are the vendor identification (8 characters) and product identification (16 characters) as reported in the inquiry data. The SAM-FS_name is the Sun StorEdge SAM-FS or Sun SAM-QFS device name as described subsequently on this man page. Trailing spaces do not need to be supplied in the vendor_id or the product_id fields. Any occurrence of a quotation mark ("), a comma (,), or a back slash (\) in any _id field should be prefaced with the escape character, which is a back slash (\). Blank lines and lines beginning with a pound character (#) are ignored. The following device names are supported within the Sun StorEdge SAM-FS and Sun SAM-QFS environments: Device Name Device Type acl2640 ACL 2640 tape library acl452 ACL 4/52 tape library adic448 ADIC 448 tape library adic100 ADIC Scalar 100 tape library adic1000 ADIC Scalar 1000 and Scalar 10K tape library archdat Archive Python 4mm DAT drive atl1500 Sun StorEdge L25 and L100 and ATL M1500 and M2500 libraries. atlp3000 ATL P3000, P4000 and P7000 tape library cyg1803 Cygnet Jukebox 1803 library dlt2000 Digital Linear Tape (2000, 4000, 7000, 8000 and SuperDLT series) drive dlt2700 Digital Linear Tape Media Changer/Stacker (2000, 4000, 7000, 8000 and SuperDLT series) docstor DISC automated library exb210 Exabyte 210 tape library exbx80 Exabyte X80 tape library exb8505 Exabyte 8505 8mm cartidge tape drive exbm2 Exabyte Mammoth-2 8mm cartidge tape drive fujitsu_128 Fujitsu M8100 128 track tape drive grauaci GRAU media library hpc7200 HP L9/L20/L60 series libraries hpc1716 HP erasable optical disk drive hpoplib HP optical library ibmatl IBM ATL library ibm0632 IBM multifunction optical disk drive ibm3570 IBM 3570 tape drive ibm3570c IBM 3570 media changer ibm3580 IBM 3580, Seagate Viper 200 and HP Ultrium (LTO) tape drives ibm3584 IBM 3584 media changer ibm3590 IBM 3590 tape drive lms4100 Laser Magnetic Laserdrive 4100 lms4500 Laser Magnetic Laserdrive 4500 metd28 Metrum D-28 tape library metd360 Metrum D-360 tape library qual82xx Qualstar 42xx, 62xx and 82xx series tape library quantumc4 Quantum PX500 and Sun StorEdge C4 tape library rap4500 Laser Magnetic RapidChanger 4500 rsp2150 Metrum RSP-2150 VHS video tape drive sonyait Sony AIT tape drive sonysait Sony Super AIT tape drive sonydms Sony Digital Mass Storage tape library sonycsm Sony CSM-20S tape library sonydtf Sony DTF tape drive speclog Spectra Logic Libraries stk4280 StorageTek 4280 Tape drive stk9490 StorageTek 9490 Tape drive stk9840 StorageTek 9840 Tape drive stktitan StorageTek Titanium Tape drive stkapi StorageTek API library stkd3 StorageTek D3 Tape drive stk97xx StorageTek 97xx Media Libraries stklxx StorageTek L20, L40, L80 and L500 Tape Libraries and Sun StorEdge L7 and L8 autoloaders. odi_neo Overland Data Inc. Neo Series Tape Libraries EXAMPLES The following is an example configuration file: "HP", "Ultrium 1", "ibm3580" # HP Ultrium Tape "HP", "Ultrium 2", "ibm3580" # HP Ultrium Tape "HP", "Ultrium 3", "ibm3580" # HP Ultrium Tape "Plasmon", "G-Enterprise","plasmong" # Plasmon G Enterprise "Plasmon", "UDO", "plasmonUDO" # Plasmon UDO 30GB optical drive "STK", "L700", "stk97xx" # STK L700 series SCSI "STK", "L180", "stk97xx" # STK L180 series SCSI "STK", "SL500", "stklxx" # STK SL500 "STK", "T10000A", "stktitan" # STK titanium drive T10000A The existence of a device in the previous example file does not imply that the device is supported by Sun StorEdge SAM-FS or Sun SAM-QFS. SEE ALSO mcf(4). NOTES Whenever a new version of Sun StorEdge SAM-FS or Sun SAM-QFS is installed, the existing inquiry.conf file is copied to inquiry.conf.MMDDYY for reference and back-up purposes. During device identification, the vendor_id and product_id values are only compared through the length of the string supplied in the inquiry.conf file. To insure an exact match, the entries should be ordered with longer names first. WARNINGS This interface is supplied to circumvent problems that occur when hardware vendors change the vendor_id and product_id values returned. For example, some hardware vendors return a different value for a product_id if the hardware is supplied by an OEM. Sun Microsystems, Inc. does not support mapping untested hardware to a Sun StorEdge SAM-FS or Sun SAM-QFS name. Sun Microsystems Last change: 03 Dec 2001 File Formats mcf(4) NAME mcf - Master configuration file for Sun StorEdge QFS, Sun StorEdge SAM-FS, and Sun SAM-QFS software SYNOPSIS /etc/opt/SUNWsamfs/mcf AVAILABILITY SUNWsamfs SUNWqfs DESCRIPTION The mcf file defines the devices and family sets used by Sun StorEdge QFS, Sun StorEdge SAM-FS, and Sun SAM-QFS software. The mcf file is read when sam-fsd is started. You can change it at any time while sam-fsd is running. The changes take effect when sam-fsd is restarted, or sent the signal SIGHUP. The following examples show an mcf file for a Sun StorEdge SAM-FS environment and an mcf file for a Sun StorEdge QFS file system. Example 1. The following is an example of a Sun StorEdge SAM-FS mcf file: # # Sun StorEdge SAM-FS file system configuration example # # Equipment Eq Eq Family Dev Additional # Identifier Or Tp Set St Parameters # --------------- -- -- ------ --- ---------- samfs1 60 ms samfs1 /dev/dsk/c1t1d0s6 61 md samfs1 - /dev/dsk/c2t1d0s6 62 md samfs1 - /dev/dsk/c3t1d0s6 63 md samfs1 - /dev/dsk/c4t1d0s6 64 md samfs1 - /dev/dsk/c5t1d0s6 65 md samfs1 - # samfs2 2 ms samfs2 /dev/dsk/c1t1d0s0 15 md samfs2 on /dev/dsk/c1t0d0s1 16 md samfs2 on # /dev/samst/c0t2d0 20 od - on /dev/samst/c1t2u0 30 rb hp30 on /usr/tmp/hp30_cat /dev/samst/c1t5u0 31 od hp30 on /dev/samst/c1t6u0 32 od hp30 on /dev/rmt/0cbn 40 od - on /dev/samst/c1t3u1 50 rb ml50 on /usr/tmp/ml50_cat /dev/rmt/2cbn 51 tp ml50 on Example 2. The following is an example of a QFS mcf file: # # Sun StorEdge QFS file system configuration example # # Equipment Eq Eq Family Dev Additional # Identifier Or Tp Set St Parameters # --------------- -- -- ------ --- ---------- # qfs1 1 ms qfs1 /dev/dsk/c1t0d0s0 11 md qfs1 on /dev/dsk/c1t1d0s5 12 md qfs1 on As the preceding examples show, each line in the mcf file is divided into six fields. The format of the fields in the mcf file is as follows: Equipment Equipment Equipment Family Device Additional Identifier Ordinal Type Set State Parameters The Equipment Identifier, Equipment Ordinal, and Equipment Type fields are required for each entry. The mcf file can contain comments. Each comment line must begin with a pound character (#). Blank lines are ignored. The fields in the file must be separated by white space. A dash character (-) can be used to indicate a field with no entry. This man page describes the content of a Sun StorEdge QFS, Sun StorEdge SAM-FS, or Sun SAM-QFS mcf file. For more configuration information, see the Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administrator's Guide. After your Sun StorEdge SAM-FS or Sun SAM-QFS software is installed, you can see more examples of mcf files in the following directory: /opt/SUNWsamfs/examples mcf File Fields This section defines the fields in the mcf file. Note that Sun StorEdge QFS environments do not include removable media devices in their mcf files. When writing the mcf file, group together the lines that define similar devices. For example, create this file such that the devices for a file system appear on consecutive lines and devices for a library appear in a separate set of consecutive lines. o The Equipment Identifier specifies a file system and its disk devices or it specifies the devices associated with an automated library. - For file system definition lines, this field can contain two types of entries. The first line in a file system definition must contain the file system name in the Equipment Identifier field, and it must be no longer than 31 characters in length. The file system name specified must be identical to the content of the Family Set field. For example: Equipment Equipment Equipment Family Device Addl Identifier Ordinal Type Set State Params ---------- ------- --------- ------ ------ ------ samqfs1 1 ms samqfs1 - - Subsequent lines in the mcf file define disk devices to be included in the file system. The Equipment Identifier fields in these lines can be no longer than 127 characters in length. - For automated library definition lines, the Equipment Identifier field contains drive identifier information and can be no longer than 127 characters in length. For example: Equipment Equipment Equipment Family Device Addl Identifier Ordinal Type Set State Params ---------- ------- --------- ------ ------ ------ /dev/rmt/0cbn 61 tp 9730 on - o The Equipment Ordinal field contains a unique number for each disk or removable media device configured. The number you specify must be in the following range: 1 < Equipment_Ordinal < 65534 Sun Microsystems recommends that you use low numbers in order to keep the internal software tables small. o The Equipment Type field contains a 2-character code that specifies the device being defined as either a disk in a file system or as a removable media device. This man page includes information on appropriate codes. o The Family Set name is an arbitrary name that you select when the mcf is created. This field can be no longer than 31 characters in length. The Family Set name defines and associates related groups of devices. This can be either a file system name, an automated library identifier, or a dash character (-), as follows: - If it is a file system name, all disk devices in the file system must use the same file system name in this field. - If it is an automated library identifier, the library and all its associated drive devices must use the same identifier. - If it is a standalone removable media device, use a dash (-) character in this field. o The Device State field defines the default status for the device at the time the system reads the mcf file. Valid values are as follows: on (default), off, unavail, or down. This field is used for disk devices, libraries, drives, and other devices. o The Additional Parameters field provides additional information. It can contain the path to a library catalog file, an interface file, or other configuration information. The Additional Parameters field can be no longer than 127 characters. For example, this field can be used to specify a nondefault location for the library catalog file. If mcf file is being configured on a SunCluster node running HA-SAM, this field must specify the library catalog file in default location. In HA-SAM configuration /var/opt/SUNWsamfs/catalog is linked to cluster filesystem which is shared among all nodes within the SunCluster. File System Disks When defining a disk cache family set, the following entries differentiate a Sun StorEdge SAM-FS file system from a Sun StorEdge QFS or Sun SAM-QFS file system: ms A Sun StorEdge SAM-FS disk cache family set. There are no meta devices. Metadata resides on the data device(s). ma A Sun StorEdge QFS or Sun SAM-QFS disk cache family set with one or more meta devices. Metadata resides on these meta devices. File data resides on the data device(s). A maximum of 252 separate magnetic disk devices can be defined for each ms or ma disk cache family set. The Family Set field is required for file system disks. It is used to define the magnetic disks that make up the family set. For a magnetic disk device, the Family Set field entry must match a Family Set defined on an ms or ma entry. The keyword shared must be specified in the Additional Parameters field if the file system is a shared file system. A shared file system is built by using the -S option to the sammkfs(1M) command. For more information on this option, see the sammkfs(1M) man page. For each disk device, the Equipment Identifier field is the path to a special file, such as /dev/dsk/cntndnsn. If the meta devices are not present on the clients in a shared file system, the keyword nodev must be specified in the Equipment Identifier field for the mm devices. The following equipment types are used to define the disk devices that reside within an ms or ma file system: mm A magnetic disk that is part of an ma disk cache family set. Metadata is allocated on this device. At least one mm device is required in an ma file system. md A magnetic disk that is part of an ms or an ma disk cache family set. This device stores data allocated in small Disk Allocation Units (DAUs) of 4 kilobytes and large DAUs of 16, 32, or 64 kilobytes. In an ms family set, this device stores metadata and file data. In an ma family set, this device stores only file data. mr A magnetic disk that is part of an ma disk cache family set. This device allocates only large DAUs for file data. gXXX A magnetic disk that is part of an ma disk cache family set. The XXX identifies a striped group of devices. This device stores data. The allocation unit is the large DAU size multiplied by the number of members in the striped group. The XXX must be a decimal number in the range 0 < XXX < 127. These devices must be the same physical size. It is not possible to use the samgrowfs(1M) command to increase the size of a striped group. However, it is possible to add additional striped groups. The Equipment Identifier is used during the mount(1M) process as the Device To Mount. The Device To Mount is the first field in /etc/vfstab file for the mount point. For more information on this, see the mount(1M), mount_samfs(1M), or vfstab(1M) man pages. SCSI-attached Libraries Several identifiers can be used to define SCSI-attached libraries in the mcf file. For each SCSI-attached library, the Equipment Identifier field must contain the path (such as /dev/samst/cntnun) to the special file for the device created by the samst device driver. For more information on the device driver, see the samst(7) man page. The Family Set field is required. It is used to associate the library controller with the drives in the library. All devices associated with the library must have the same Family Set name. The Additional Parameters field is optional. This field can be used to specify a nondefault location for the library catalog file. By default, catalogs are written to /var/opt/SUNWsamfs/catalog/family_set_name. This file is used to store information about each piece of media in the library. In HA-SAM configuration, this field must specify the library catalog file in default location and /var/opt/SUNWsamfs/catalog is linked to cluster filesystem which is shared among all nodes within the SunCluster. The following Equipment Type field entries can be used to define manually mounted or automated libraries that are attached through a SCSI interface: Equipment Type Field Content Definition rb Generic SCSI library that is automatically configured by Sun StorEdge SAM-FS or Sun SAM-QFS software. NOTE: An rb definition is preferred for all SCSI-attached libraries. The remainder of the library definitions in this list are supported but are not recommended for use in an mcf file. If a library in this list is defined in the mcf file as rb, Sun StorEdge SAM-FS and Sun SAM-QFS set the appropriate type based on the SCSI vendor code. ad ADIC Scalar 448 libraries. ae ADIC Scalar 100 libraries. al Sun StorEdge L25 and L100 and ATL M1500 and M2500 libraries. as ADIC Scalar 1000 and Scalar 10K libraries. q8 Qualstar 42xx, 62xx, 82xx, TLS and RLS series libraries ov Overland Data Inc. Neo Series Tape Libraries. ac ATL Products 4/52, 2640, 7100, and P-series tape libraries, and Sun 1800, 3500, L1000 and L11000 tape libraries. cy Cygnet optical disk libraries. ds DocuStore and Plasmon optical disk libraries. eb Exabyte 210, Sun L280, and ATL Products L-series tape libraries. e8 Exabyte X80 libraries. hc HP L9/L20/L60 series hp Hewlett Packard optical disk libraries. ic IBM 3570 media changer. me Metrum and Mountain Gate libraries. pd Plasmon D-Series DVD-RAM libraries. pg Plasmon G-Series UDO/MO libraries. The library must be configured to G-Enterprise mode, element address scheme 1 and barcode type 2 or 3 by using the front panel. ml Quantum DLTx700 tape libraries. dm Sony DMF and DMS libraries. cs Sony CSM-20S Tape Library. sl Spectra Logic and Qualstar tape libraries. s9 StorageTek 97xx series libraries. sn StorageTek L20, L40, L80, and L500 tape libraries and Sun StorEdge L7 and L8 autoloaders. c4 Quantum PX500 and Sun StorEdge C4 libraries. These libraries are supported in native mode (PX500) only. SAM-QFS does not support these libraries in M1500 emulation mode. il IBM 3584 tape libraries. Network-attached Libraries This subsection describes how to define a network-attached library in your mcf file. For each Network-attached library, the Equipment Identifier field must contain the path to the "parameters file" for the device. The Family Set field is required. It is used to associate devices with the library. All devices associated with the library must have the same Family Set name. The Additional Parameters field is optional. This field can be used to specify a nondefault location for the library catalog file. By default, catalogs are written to /var/opt/SUNWsamfs/catalog/family_set_name. This file is used to store information about each piece of media in the library. In HA-SAM configuration, this field must specify the library catalog file in default location and /var/opt/SUNWsamfs/catalog is linked to cluster filesystem which is shared among all nodes within the SunCluster. The network-attached library definitions are as follows: Equipment Type Field Content Definition gr ADIC/GRAU Network-attached library. The Equipment Identifier field must contain the path to the parameters file for the grauaci interface. For more information, see the grauaci(7) man page. fj Fujitsu LMF library. The Equipment Identifier field must contain the path to the parameters file for the fujitsulmf interface. For more information, see the fujitsulmf(7) man page. im IBM 3494 interface. The Equipment Identifier field must contain the path to the parameters file for the ibm3494 interface. For more information, see the ibm3494(7) man page. pe Sony network-attached interface. The Equipment Identifier field must contain the path to the parameters file for the sony interface. For more information, see the sony(7) man page. sk StorageTek ACSLS interface. The Equipment Identifier field must contain the path to the parameters file for the ACSLS interface. For more information, see the stk(7) man page. The Historian The hy identifier in the Equipment Type field identifies the Sun StorEdge SAM-FS or Sun SAM-QFS historian. The Equipment Identifier field must contain the string historian. The Family Set must contain a dash character (-). The Additional Parameters field is optional. This field can be used to specify a nondefault location for the historian. By default, the historian is written to /var/opt/SUNWsamfs/catalog/historian. This file is used to store information about the media handled by the historian. For more information, see the historian(7) man page. Optical Disk Drives This subsection describes the optical disk drive devices supported by Sun StorEdge SAM-FS and Sun SAM-QFS. NOTE that optical disk drive devices are not supported on x64 platforms. In the mcf file, a line describing an optical device must contain the following: o The Equipment Identifier field must be the path to the special file, such as /dev/samst/cntnun, for the samst device driver. For more information, see the samst(7) man page. o The Family Set field is used to associate the drive with the library that has the same Family Set. If the family set is defined as a dash (-), the drive is assumed to be manually loaded. o The Equipment Type field contains the optical drive identifier, as follows: Equipment Type Field Content Definition od Generic optical disk. A disk that is automatically configured by Sun StorEdge SAM-FS or Sun SAM-QFS. If you specify od, Sun StorEdge SAM-FS or Sun SAM-QFS sets the appropriate type based on the SCSI vendor code. NOTE that an od definition is preferred for all optical drives. If you specify od in the Equipment Type field, the Sun StorEdge SAM-FS or Sun SAM-QFS software sets the appropriate type based on the SCSI vendor code. The remainder of the definitions in this list are supported but are not recommended for use in an mcf file. o2 12 inch WORM drive. wo 5 1/4 inch optical WORM drive. mo 5 1/4 inch erasable optical drive. The Sun StorEdge SAM-FS and Sun SAM-QFS environments support disks with 512-, 1024-, and 2048-byte sectors. pu Plasmon UDO drive. mf IBM Multi Function optical drive. Note that for all magneto-optical media, the default archmax value is 5 megabytes. Tape Drives This subsection describes the set of tape drives supported by Sun StorEdge SAM-FS or Sun SAM-QFS software for use in manually mounted and automated libraries. A line in the mcf file for a tape drive must contain information in the following other fields: o The Equipment Identifier must be the path to the raw device, typically, /dev/rmt/nbn. However, it can be any symbolic link that also points to the proper special file in the /devices tree. You must specify the BSD no-rewind path. If the device supports compression, then that path should be specified for better tape usage; except if the ST_AUTODEN_OVERRIDE drive option bit is set in an st.conf entry, you cannot specify a compression preference by changing the dev entry. Any attempt to specify compression is ignored. This is determined by the Solaris SCSI tape driver, st. The compression state of the drive is determined by its power-on default. For more information, see the mtio(7) man page. o The Family Set field must be used to associate the device with the library that has the same Family Set name. If the family set is a dash character (-), then the device is assumed to be a manually loaded device. o The Additional Parameters is required for a tape drive if the Equipment Identifier field does not contain information in a /dev/rmt/* format (the standard st device driver). If specified, the Additional Parameters field must contain the path to the special file, such as /dev/samst/cntnun, for the samst device driver. For more information, see the samst(7) man page. If Sun StorEdge SAM-FS or Sun SAM-QFS has access to a tape device, no other user should be allowed access the device during that period. Sun StorEdge SAM-FS and Sun SAM-QFS change the mode on the path supplied in the mcf file to 0660 at startup, or when the device state moves from down to on. When the state moves from on to down, the mode is set to the value of tp_mode in the defaults.conf file. For more information, see tbe defaults.conf(4) man page. The following list shows the tape drives for each type of tape media supported. The tape drives supported by Sun StorEdge SAM-FS and Sun SAM-QFS are as follows: Equipment Type Field Content Definition tp Generic tape drive. These tapes are automatically configured by Sun StorEdge SAM-FS or Sun SAM-QFS. NOTE that a tp definition is preferred for all tape drives. If you specify tp in the Equipment Type field, the Sun StorEdge SAM-FS or Sun SAM-QFS software sets the appropriate type based on the SCSI vendor code. The remainder of the definitions in this list are supported but are not recommended for use in an mcf file. dt DAT 4mm tape drive. In the defaults.conf file, the default block size keyword for this media is dt_blksize = 16. lt Digital linear tape (DLT) drive (including Super DLT and DLT-S4). In the defaults.conf file, the default block size keyword for this type of media is lt_blksize = 128. xt Exabyte (850x) 8mm tape drive. In the defaults.conf file, the default block size keyword for this media is xt_blksize = 16. xm Exabyte Mammoth-2 8mm tape drive. In the defaults.conf file, the default block size keyword for this media is xm_blksize = 128. fd Fujitsu M8100 128-track tape drive. In the defaults.conf file, the default block size keyword for this media is fd_blksize = 256. i7 IBM 3570 tape drive. In the defaults.conf file, the default block size keyword for this media is i7_blksize = 128. li IBM 3580, Seagate Viper 200 and HP Ultrium (LTO) In the defaults.conf file, the default block size keyword for this media is li_blksize = 256. ib IBM 3590 tape drive. In the defaults.conf file, the default block size keyword for this media is ib_blksize = 256. m2 IBM 3592 J1A and E05 tape drives. In the defaults.conf file, the default block size keyword for this media is m2_blksize = 2048. vt Metrum VHS (RSP-2150) tape drive. In the defaults.conf file, the default block size keyword for this media is vt_blksize = 128. at Sony AIT tape drive. In the defaults.conf file, the default block size keyword for this media is at_blksize = 128. sa Sony Super AIT tape drive. In the defaults.conf file, the default block size keyword for this media is sa_blksize = 2048. so Sony DTF tape drive. In the defaults.conf file, the default block size keyword for this media is so_blksize = 1024. st StorageTek 3480 tape drive. In the defaults.conf file, the default block size keyword for this media is st_blksize = 128. se StorageTek 9490 tape drive. In the defaults.conf file, the default block size keyword for this media is se_blksize = 128. sg StorageTek 9840 tape drive. In the defaults.conf file, the default block size keyword for this media is sg_blksize = 256. d3 StorageTek D3 tape drive. In the defaults.conf file, the default block size keyword for this media is d3_blksize = 256. sf StorageTek T9940 tape drive. In the defaults.conf file, the default block size keyword for this media is sf_blksize = 256. ti StorageTek Titanium tape drive. In the defaults.conf file, the default block size keyword for this media is ti_blksize = 2048. For all tapes, the Sun StorEdge SAM-FS or Sun SAM-QFS system sets the block size to a media-specific default. For information on how to change the default block size, see the defaults.conf(4) man page. For all tapes, the default archmax value is 512 megabytes. Disk Archiving The archiver can be configured to archive directly to online disk cache. To enable disk archiving, you must perform the following steps: 1. Create directories in online disk cache to serve as destinations for the archive copies. 2. Create the /etc/opt/SUNWsamfs/diskvols.conf file. 3. Edit the archiver.cmd file and add the -disk_archive directive. The media type for a disk volume is dk. The block size for a disk volume is dk_blksize=1024. This value cannot be changed. The media type for a Sun StorageTek 5800 Storage System disk volume is cb. The 5800 schema specifies the metadata attributes that are stored with objects in the 5800 system. The system comes preconfigured with a default metadata schema. For a 5800 disk volume you must modify the default schema file to add metadata specific to SAM-FS. For more information on configuring the schema, refer to the Sun StorageTek 5800 System Adminstration Guide. The file /opt/SUNWsamfs/examples/metadata_config_samfs.xml can be used to extend the default schema for SAM-FS. Disk archiving is explained in more detail in the Sun StorEdge QFS and Sun StorEdge SAM-FS Installation and Configuration Guide and in the Sun StorEdge SAM-FS Storage and Archive Management Guide. SAM-Remote Device Definitions Several identifiers define devices when using the Sun SAM-Remote client or Sun SAM-Remote server software. For more information on configuring the Sun SAM-Remote client or the Sun SAM-Remote server, see the sam-remote(7) man page or see the Sun SAM-Remote Administrator's Guide. The identifiers used when configuring the Sun SAM-Remote client or Sun SAM-Remote server are as follows: Equipment Type Field Content Definition ss Sun SAM-Remote server. The Equipment Identifier field must contain the path name to the server configuration file. The Family Set field must identify the server. That is, it must be the same as the Family Set name of the server. It must match the name used in the client side definition. It is used by the clients to associate the device with the server of the same Family Set name. sc Sun SAM-Remote client. The Equipment Identifier field must contain the path name to the client configuration file. The Family Set field must contain an identifier that is the same as the family set name of the server. It is used by the clients to associate the device with the server of the same Family Set name. The Additional Parameters field must contain the full path name of the client's library catalog file. rd Sun SAM-Remote pseudo-device. The Equipment Identifier field must be the path to the pseudo-device, such as /dev/samrd/rd2. The Family Set field must be the name of the server. It is used by the clients to associate the device with the server of the same Family Set name. FILES /opt/SUNWsamfs/examples Contains example mcf files. SEE ALSO Sun SAM-Remote Administrator's Guide. Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administrator's Guide. Sun StorEdge SAM-FS Storage and Archive Management Guide. chmod(1). build_cat(1M), dump_cat(1M), mount(1M), mount_samfs(1M), sammkfs(1M). sam-fsd(1M), defaults.conf(4), inquiry.conf(4), vfstab(4). dst(7), fujitsulmf(7), grauaci(7), historian(7), ibm3494(7), mtio(7), sam-remote(7), samst(7), sony(7), st(7), stk(7). Sun Microsystems Last change: 07 Feb 2007 File Formats notify.cmd(4) NAME notify.cmd - Sun StorageTek QFS or Sun StorageTek SAM email subscriptions commands file SYNOPSIS /etc/opt/SUNWsamfs/notify.cmd AVAILABILITY SUNWsamfs DESCRIPTION The Sun StorageTek QFS or Sun StorageTek SAM system has the ability to inform a user of certain events or conditions by generating a message and automatically sending email notifi- cations. The /etc/opt/SUNWsamfs/notify.cmd stores the email addresses for the following notifications: No space available on file system (ENospace), Recovery Point warnings (DumpWarn), Recovery Point errors (DumpInterrupted), File System exceeded its high water mark (HwmExceeded), ACSLS configura- tion warnings (AcslsWarn), and ACSLS configuration errors (AcslsErr). The email subscriptions are added, modified and deleted only via the File System Manager software, a browser-based graph- ical user interface to the Sun StorageTek QFS or Sun StorageTek SAM software. This file is created automatically after installation and 'root' is assigned as the default subscriber for all notifi- cations. If you would like to add, modify or delete subscriptions, use the Email Alerts feature in the File System Manager software. To preserve compatibility, the email subscriptions for Archiving is Interrupted, Recycling is complete, Library or Tape drive is down and, Requested volume is unavailable, are automatically added to the /etc/opt/SUNWsamfs/scripts/archiver.sh (1M), /etc/opt/SUNWsamfs/scripts/recycler.sh (1M), /etc/opt/SUNWsamfs/scripts/dev_down.sh (1M), and /etc/opt/SUNWsamfs/scripts/load_notify.sh (1M) respectively. MANUAL EDITING The /etc/opt/SUNWsamfs/notify.cmd consists of the notifica- tion type followed by the list of email addresses that have subscribed to it. Each notification type and its respective subscriber list are space separated, while the email addresses are comma separated. It is is highly recommended that you only use the File Sys- tem Manager software to add, modify, or delete subscrip- tions, but if you must manually modify this file, take care to preserve the formatting of this file. EXAMPLE The following is an example /etc/opt/SUNWsamfs/notify.cmd file: DumpInterrupted root, samadmin@xxx ENospace root HwmExceeded The above entries indicate that root is to receive email notifications if the File System is full or if errors are encountered when taking recovery points. There are no sub- scribers for the 'File System exceeded its high water mark' notification. To remove 'root' as a subscriber, the file should now read as follows: DumpInterrupted samadmin@xxx ENospace HwmExceeded SEE ALSO sendtrap(1M). defaults.conf(4). Sun Microsystems Last change: 12 Jan 2007 File Formats nrecycler.cmd(4) NAME nrecycler.cmd - Sun StorEdge SAM-FS or Sun SAM-QFS sam-nrecycler commands file SYNOPSIS /etc/opt/SUNWsamfs/nrecycler.cmd AVAILABILITY SUNWsamfs DESCRIPTION Commands for controlling sam-nrecycler(1M) are read from /etc/opt/SUNWsamfs/nrecycler.cmd. These commands are given one per line. logfile = filename Set the name of the log file to filename. SAMFSDUMP DEFINITIONS SECTION The samfsdumps and endsamfsdumps directives delimit this section of the nrecycler.cmd file. The samfsdump definitions section defines the SAM-FS dump files for archiver retention capabilities. Each line speci- fies the path to a directory containing SAM-FS dump files. The user is responsible for making sure the list of direc- tories is complete and all SAM-FS dumps files are contained in the directory list. The nrecycler cannot validate the SAM-FS dump file list. EXAMPLE The following is an example /etc/opt/SUNWsamfs/nrecycler.cmd file: samfsdumps /samdumps endsamfsdumps SEE ALSO sam-nrecycler(1M). Sun Microsystems Last change: 12 Jan 2004 File Formats preview.cmd(4) NAME preview.cmd - Sun StorEdge SAM-FS or Sun SAM-QFS preview directives file SYNOPSIS /etc/opt/SUNWsamfs/preview.cmd AVAILABILITY SUNWsamfs DESCRIPTION An archive or stage request for a volume that is not currently loaded goes to the preview area for future consideration. A user can control the scheduling of preview requests, thus overriding the default behavior, by entering directives in the preview.cmd file. The preview.cmd file contains directives for modifying preview request priorities. The directives allow users to increase the priority for specific VSNs and change archive request priorities based on the file system states regarding High Water Mark (HWM) and Low Water Mark (LWM). These directives are read by sam-amld at start-up time, and all values specified are stored in shared memory. The priority specifications cannot be changed while the sam-amld daemon is running. The preview.cmd file can contain comments. A comment begins with a pound character (#) and extends through the end of the line. DIRECTIVES The directives in the preview.cmd file are specified one per line. With regard to their placement within the preview.cmd file, there are two types of directives: o Global directives. These directives apply to all file systems. Directives are assumed to be global if they appear in the preview.cmd file prior to any fs = directives. o Directives specific to a particular file system. File system specific directives must appear after the global directives in the preview.cmd file. A directive line with the following form names a specific file system and indicates that all subsequent directives apply only to that file system: fs = file_system_family_set_name A subsequent fs = directive in the preview.cmd file declares a set of directives that apply to another file system. File system specific directives override general directives. Some directives can be used as both global and file system specific directives. This can be useful, for example, if you want to specify the hwm_priority directive globally to apply to most Sun StorEdge SAM-FS or Sun SAM-QFS file systems but you also want to use it as a file system specific directive to specify a different value for one particular file system. The following sections describe the directives that can appear in a preview.cmd file. You can specify either an integer or a floating point value as an argument to the _priority directives, but the system stores the value as a floating point value internally. GLOBAL DIRECTIVES Global directives must appear in the preview.cmd file before any fs = directives. They cannot appear after an fs = directive. The global directives are as follows: vsn_priority = value This directive specifies the value by which the priority is to increase for VSNs marked as high- priority VSNs. For more information, see the chmed(1M) man page. The vsn_priority = 1000.0 by default. age_priority = factor This global directive specifies a factor to to be applied to the time (in seconds) that a request is allowed to wait in the preview area to be satisfied. The factor is as follows: o A factor > 1.0, increases the weight of the time when calculating the total priority. o A factor < 1.0, decreases the weight of the time when calculating the total priority. o A factor = 1.0 has no effect on the default behavior. The age_priority = 1.0 by default. For more information, see the PRIORITY CALCULATION section of this man page. FILE SYSTEM SPECIFIC DIRECTIVE The fs = directive specifies a particular file system and applies only to that specified file system. This directive's syntax is as follows: fs = file_system_family_set_name This directive indicates that the subsequent directives apply only to the indicated file_system_family_set_name. GLOBAL OR FILE SYSTEM SPECIFIC DIRECTIVES Several directives can be used either globally or as file system specific directives. These directives are as follows: hwm_priority = value This directive indicates the value by which the priority is to increase for archiving requests versus staging after the file system crosses the HWM level. This means that the releaser is running. The hwm_priority = 0.0 by default. hlwm_priority = value This directive indicates the value by which the priority is to increase for archiving requests versus staging. This directive is effective when the file system is emptying, and the amount of data is between the HWM and the LWM. Because the file system is emptying, you may want to give priority to loads for stage requests. The hlwm_priority = 0.0 by default. lhwm_priority = value This directive indicates the value by which the priority is to increase for archiving requests versus staging. This directive is effective when the file system is filling up, and the amount of data is between the HWM and the LWM. Because the file system is filling up, you may want to give priority to loads for archive requests. The lhwm_priority = 0.0 by default. lwm_priority = value This directive specifies the value by which the priority is to increase for archiving requests versus staging when the file system is below the LWM level. The lwm_priority = 0.0 by default. PRIORITY CALCULATION The total preview request priority is the sum of all priorities and is calculated as follows: Total priority = vsn_priority + wm_priority + age_priority * time_in_sec The wm_priority in the previous equation refers to whichever condition is in effect at the time, either hwm_priority, hlwm_priority, lhwm_priority, or lwm_priority. All priorities are stored as floating point numbers. EXAMPLES Example 1. This example preview.cmd file sets both the vsn_priority and hwm_priority for the samfs1 file system. Other Sun StorEdge SAM-FS or Sun SAM-QFS file systems not specified here use the default priority for the HWM. All file systems use the default priorities for the LWM and the state between LWM and HWM. vsn_priority = 1000.0 fs = samfs1 hwm_priority = 100.0 Example 2. The next example preview.cmd file sets priority factors for all Sun StorEdge SAM-FS or Sun SAM-QFS file systems, but it sets an explicit and different HWM priority factor for the samfs3 file system. hwm_priority = 1000.0 hlwm_priority = -200.0 lhwm_priority = 500.0 fs = samfs3 hwm_priority = 200.0 SEE ALSO chmed(1M), sam-amld(1M). Sun Microsystems Last change: 03 Dec 2001 File Formats recycler.cmd(4) NAME recycler.cmd - Sun StorEdge SAM-FS or Sun SAM-QFS sam-recycler commands file SYNOPSIS /etc/opt/SUNWsamfs/recycler.cmd AVAILABILITY SUNWsamfs DESCRIPTION Commands for controlling sam-recycler(1M) are read from /etc/opt/SUNWsamfs/recycler.cmd. These commands are given one per line. logfile = filename Set the name of the log file to filename. This file shows the overall media utilization and a sorted list of VSNs in the order in which they will be recycled. The default is no log file. See sam-recycler(1M) for more information. no_recycle media-type VSN-regexp [VSN-regexp...] Disallow sam-recycler(1M) from recycling the VSNs which match the media-type and the regular expression(s), VSN-regexp. robot-family-set parameters This command sets recycling parameters for a particular library identified by robot-family-set (this is the name given as the fourth field in the /etc/opt/SUNWsamfs/mcf file line defining the library for which you wish to set the parameters). parameter can be one more of the following: -dataquantity size This parameter sets a limit of size bytes on the amount of data the recycler will schedule for rearchiving in order to clear volumes of useful data. Note that the actual number of volumes selected for recycling may also be dependent on the -vsncount parameter. The default is 1 giga- byte (1G). -hwm percent establishes the high-water mark for the media utilization in the indicated library, specified as an integer percentage of total capacity. When the utilization of those volumes exceeds percent, sam-recycler(1M) will begin to recycle the library. The default is 95. -ignore will keep sam-recycler(1M) from selecting any can- didates from the specified library. The intent of this parameter is to allow a convenient way of testing other parameters. -mail mailaddress will cause sam-recycler(1M) to mail a message to the indicated mailaddress when a library's media utilization exceeds the high-water mark. Omission of mailaddress prevents recycling. If you specify -mail, you must specify a valid mailaddress. -mingain percent This parameter limits selection of volumes for recycling to those which would increase their free space by percent or more. Volumes not meeting the -mingain parameter are not recycled. The default is 50. -vsncount count This parameter sets a limit of count on the number of volumes the recycler will schedule for rear- chiving in order to clear volumes of useful data. Note that the actual number of volumes selected for recycling may also be dependent on the -data- quantity parameter. The default is 1. To preserve compatibility with pre-existing /etc/opt/SUNWsamfs/recycler.cmd files, an alternative, less powerful, syntax is allowed for the library recycling param- eters command. robot-family-set robot-high-water VSN-minimum-percent-gain options This command sets recycling parameters for a particular library identified by robot-family-set (this is the name given as the fourth field in the /etc/opt/SUNWsamfs/mcf file line defining the library for which you wish to set the parameters). robot- high-water establishes the high-water mark for the media utilization in the indicated library, specified as an integer percentage of total capacity. When the utilization of those volumes exceeds percent, sam- recycler(1M) will begin to recycle the library. The VSN-minimum-percent-gain (aka min-gain) value specifies a threshold of space available to be reclaimed (as an integer percent of total capacity of the VSN) below which VSNs will not be selected for recycling. The options consist of zero or more of the following: ignore - which will keep sam-recycler(1M) from select- ing any candidates from the specified library. mail mailaddress - which will cause sam-recycler(1M) to mail a message to the indicated mailaddress when a library's media utilization exceeds the high-water mark. Omission of mailaddress prevents any mail from being sent. script = filename Supply the name of the file executed when a volume is to be relabeled. The default is /etc/opt/SUNWsamfs/scripts/recycler.sh ARCHIVER'S COMMAND FILE The archiver's command file, /etc/opt/SUNWsamfs/archiver.cmd, can also specify recycling parameters for archive sets. Each archive set which has recycling parameters applied in /etc/opt/SUNWsamfs/archiver.cmd will be considered as a pseudo library containing just the VSNs which the archiver assigns to the archive set. See archiver.cmd(4) for more information. Archive set names may not be specified in the /etc/opt/SUNWsamfs/recycler.cmd file. DEFAULT FILE If there is no /etc/opt/SUNWsamfs/recycler.cmd file, then, for each library, a line is constructed: library -dataquantity 1G -hwm 95 -ignore -mail root -mingain 50 -vsncount 1 and logging is disabled. EXAMPLE The following is an example /etc/opt/SUNWsamfs/recycler.cmd file: logfile = /var/adm/recycler.log lt20 -hwm 75 -mingain 60 -ignore hp30 -hwm 90 -mingain 60 -mail root gr47 -hwm 95 -mingain 60 -ignore mail root no_recycle lt DLT.* The results of sam-recycler(1M) operation are found in /var/adm/recycler.log. Three libraries are defined with various high-water marks. The first library is not recy- cled, but the usage information for the VSNs it contains will appear in the log, and no mail will be generated. The second library is recycled (that is, VSNs are emptied of valid archive images and relabeled) and root is sent e-mail when the library exceeds the 90% high-water mark. The third library is not recycled, but root is notified if usage exceeds the high-water mark. For hp30, only VSNs whose recycling would free up at least 60% of the capacity of the VSN are considered. No medium which is of media type lt and whose VSN begins with DLT will be recycled. SEE ALSO sam-recycler(1M). archiver.cmd(4), mcf(4). Sun Microsystems Last change: 12 Jan 2004 File Formats releaser.cmd(4) NAME releaser.cmd - Sun StorEdge SAM-FS and Sun SAM-QFS releaser command file SYNOPSIS /etc/opt/SUNWsamfs/releaser.cmd AVAILABILITY SUNWsamfs DESCRIPTION Directives for controlling the releaser can be read from the /etc/opt/SUNWsamfs/releaser.cmd file. The directives must appear one per line. Comment lines are permitted. Comment lines must begin with a pound character (#), and the comment can extend through the rest of the line. Directives that appear prior to any fs= directive are applied to all file systems. Directives that appear after a fs= directive are applied to the specified file system only. Directives that are specific to a file system override general directives. The directives on this man page are divided into groups. The weight directives for size and age determine the release priority of a file. The miscellaneous directives control whether a log file is written, whether there is a minimum age required for files, and other aspects of releasing. WEIGHT DIRECTIVES The following weights are used to calculate the release priority of each file in the file system. Each file's priority is composed of two parts: size priority and age priority. The size priority plus the age priority equals the file's total release priority. Size Priority The size priority is determined by the value of the weight_size directive. This directive has the following format: weight_size=weight_size_value Sets the weight factor for the size of the file to weight_size_value. Specify a floating-point number in the following range: 0.0 < weight_size_value < 1.0. The default is 1.0. The weight_size_value is multiplied by the size of the file in 4-kilobyte blocks to arrive at the size component of the file's release priority. Age Priority The age priority can be calculated in one of the following ways: o The first method multiplies the value of the weight_age= directive by the most recent of the following ages: access age, modify age, and residence change age. The access age is defined as the current time minus the file's last access time. The weight_age directive has the following format: weight_age=weight_age_value Sets the weight factor for the overall age of the file to weight_age_value. The weight_age_value is multiplied by the most recent of the file's access, modify or residence change age to arrive at the age component of the file's release priority. Specify a floating-point number in the following range: 0.0 < weight_age_value < 1.0. The default is 1.0. If you specify a weight_age= directive for a given file system, you cannot specify weight_age_access=, weight_age_modify=, or weight_age_residence= directives for the same file system. o The second method allows you to specify separate weights for the access, modify, and residence ages. The ages are calculated in units of 60-second minutes. If you want to specify separate weights for the access, modify, and residence ages, use the following directives in the releaser.cmd file: weight_age_access=weight_age_access_value Sets the weight factor for the access age of the file to weight_age_access_value. Specify a floating-point number in the following range: 0.0 < weight_age_access < 1.0. The default is 1.0. The weight_age_access_value is multiplied by the file's access age (expressed in minutes). This product, added to the sum of the products of the modify and residence-change ages multiplied by their respective weights, becomes the age component of the file's release priority. If you specify a weight_age= directive for a given file system, you cannot specify a weight_age_access= directive for the same file system. weight_age_modify=weight_age_modify_value Sets the weight factor for the modify age of the file to weight_age_modify_value. Specify a floating-point number in the following range: 0.0 < weight_age_modify < 1.0. The default is 1.0. The weight_age_modify_value is multiplied by the file's modify age (expressed in minutes). This product, added to the sum of the products of the modify and residence-change ages multiplied by their respective weights, becomes the age component of the file's release priority. If you specify a weight_age= directive for a given file system, you cannot specify a weight_age_modify= directive for the same file system. weight_age_residence=weight_age_residence_value Sets the weight factor for the residence-change age of the file to weight_age_residence_value. Specify a floating-point number in the following range: 0.0 < weight_age_residence < 1.0. The default is 1.0. The weight_age_residence_value is multiplied by the file's residence-change age (expressed in minutes). This product, added to the sum of the products of the modify and residence-change ages multiplied by their respective weights, becomes the age component of the file's release priority. If you specify a weight_age= directive for a given file system, you cannot specify a weight_age_residence= directive for the same file system. MISCELLANEOUS DIRECTIVES The following miscellaneous directives can be specified in the releaser.cmd file: fs = file_system_family_set_name Specifies to the releaser that the subsequent directives apply to the indicated file_system_family_set_name only. list_size = number Sets the number of candidate files for release during one pass of the file system. For number, specify an integer number in the following range: 10 < number < 2,147,483,648 The default is 10000. If you have many small files in your file system you may want to increase this number. no_release Prevents the releaser from releasing any files. This directive is useful when you are tuning the priority weights. Also see the display_all_candidates directive. By default, files are released. rearch_no_release Prevents the releaser from releasing files marked to be rearchived. By default, files marked for rearchive are released. logfile = filename Sets the name of the releaser's log file to filename. By default, no log file is written. display_all_candidates Writes the releaser priority for each file, as it is encountered, to the log file. This can be useful in tuning when used in conjunction with the no_release directive. This directive allows you to judge the effect of changing the priority weights. By default file priority is not displayed in any way. min_residence_age = time Sets the minimum residency age to time seconds. This is the minimum time a file must be online before it is considered to be a release candidate. The default is 600 seconds (10 minutes). EXAMPLES Example 1. This example file sets the weight_age= and weight_size= directives for the samfs1 file system. No releaser log is produced. fs = samfs1 weight_age = .45 weight_size = 0.3 Example 2. This example provides weights for all file systems. All file system releaser runs are logged to /var/adm/releaser.log. weight_age = 1.0 weight_size = 0.03 logfile = /var/adm/releaser.log Example 3. This example specifies weights and log files for each file system. logfile = /var/adm/default.releaser.log fs = samfs1 weight_age = 1.0 weight_size = 0.0 logfile = /var/adm/samfs1.releaser.log fs = samfs2 weight_age_modify = 0.3 weight_age_access = 0.03 weight_age_residence = 1.0 weight_size = 0.0 logfile = /var/adm/samfs2.releaser.log Example 4. This example is identical in function to example 3, but it specifies the weight_size= and list_size= directives globally. logfile = /var/adm/default.releaser.log weight_size = 0.0 list_size = 100000 fs = samfs1 weight_age = 1.0 logfile = /var/adm/samfs1.releaser.log fs = samfs2 weight_age_modify = 0.3 weight_age_access = 0.03 weight_age_residence = 1.0 logfile = /var/adm/samfs2.releaser.log SEE ALSO release(1). sam-releaser(1M). Sun Microsystems Last change: 06 Jan 2003 File Formats rft.cmd(4) NAME rft.cmd - Sun StorEdge SAM-FS or Sun SAM-QFS file transfer server directives file (was ftp.cmd) SYNOPSIS /etc/opt/SUNWsamfs/rft.cmd AVAILABILITY SUNWsamfs DESCRIPTION Directives for controlling the Sun StorEdge SAM-FS or Sun SAM-QFS file transfer server are read from /etc/opt/SUNWsamfs/rft.cmd. In the rft.cmd file, each directive must appear on its own line. Each directive has the following format: keyword = value Comment lines can appear in the rft.cmd file. A pound sign (#) in column 1 indicates a comment line. The rft.cmd file accepts the following directives: logfile = filename Sets the name of the rft log file to filename, specified as an absolute pathname. By default, no log file is written. The rft log file contains a line for each file transferred. The line contains the date, time, and the name of the file. tcpwindow = size Sets the TCP window size for the data connection. size may be specified with the suffixes 'b', 'k', 'M', 'G', and 'T', for bytes, kilobytes, megabytes, gigabytes, and terabytes. The default unit size is bytes. The default value is 0. blksize = size Sets the amount of data to send down the socket at a time. size may be specified with the suffixes 'b', 'k', 'M', 'G', and 'T', for bytes, kilobytes, megabytes, gigabytes, and terabytes. The default unit size is bytes. The default value is 1024K bytes. EXAMPLES The following is an example /etc/opt/SUNWsamfs/rft.cmd file: logfile = /var/opt/SUNWsamfs/log/rft The results of the rft file transfer daemon's operations are found in /var/opt/SUNWsamfs/log/rft. FILES The following files are used by the file transfer server: /etc/opt/SUNWsamfs/rft.cmd File transfer server command file. SEE ALSO sam-rftd(1M). Sun Microsystems Last change: 04 AUG 2003 File Formats samfs.cmd(4) NAME samfs.cmd - Defines mount parameters for Sun StorEdge SAM-FS, Sun StorEdge QFS, and Sun SAM-QFS file systems SYNOPSIS /etc/opt/SUNWsamfs/samfs.cmd AVAILABILITY SUNWqfs SUNWsamfs DESCRIPTION Commands for controlling samfs mount parameters are read from /etc/opt/SUNWsamfs/samfs.cmd. These commands serve as defaults, and can be superseded by parameters on the mount command. See mount_samfs(1M). The /etc/opt/SUNWsamfs/samfs.cmd file is read when sam-fsd is started. You can change it at any time while sam-fsd is running. The changes take effect when sam-fsd is restarted, or sent the signal SIGHUP via the samd config command. When changing mount options in this file, you must unmount and mount the file system in order for the new mount options to take effect. These commands are given one per line. Comments begin with a # and extend through the end of the line. Commands given before any "fs =" line apply in general to all filesystems; "fs =" introduces commands which are specific to the men- tioned filesystem only. Filesystem-specific commands over- ride general commands. COMMANDS See mount_samfs(1M) under OPTIONS for the list of supported commands. The following additional command is available as well. fs = fs_name This command specifies the following commands apply only to the indicated file system with family set name fs_name. EXAMPLE This example file sets high and low for 2 different filesys- tems, samfs1 and samfs2. fs = samfs1 high = 90 low = 80 fs = samfs2 high = 80 low = 75 SEE ALSO release(1), setfa(1). mount_samfs(1M), sam-fsd(1M), sam_releaser(1M). sam_advise(3), sam_setfa(3). directio(3C). mcf(4). Sun Microsystems Last change: 03 Dec 2001 File Formats sefdata(4) NAME sefdata - Collects System Error Facility (SEF) data for Sun StorEdge SAM-FS and Sun SAM-QFS file systems SYNOPSIS /var/opt/SUNWsamfs/sef/sefdata #include "/opt/SUNWsamfs/include/sefvals.h" #include "/opt/SUNWsamfs/include/sefstructs.h" AVAILABILITY SUNWsamfs DESCRIPTION The sefdata file contains the data gathered from the log sense pages of peripheral tape devices used by Sun StorEdge SAM-FS and Sun SAM-QFS file systems. Each time the Sun StorEdge SAM-FS or Sun SAM-QFS software unloads a cartridge from a drive, pertinent log sense pages are obtained from the device, and a record is written to the sefdata file. Each record consists of a header followed by some number of log sense pages. The record header has the format of a sef_hdr structure. This structure is defined in /opt/SUNWsamfs/include/sefstructs.h, and it has the following components: struct sef_hdr { uint_t sef_magic; /* magic # for app to sync file posn */ uint_t sef_version; /* version number */ uint_t sef_size; /* size of this record, excl. header */ uint16_t sef_eq; /* equipment number of this device */ char sef_devname[128]; /* pathname of device */ uchar_t sef_vendor_id[9]; /* vendor id from inquiry */ uchar_t sef_product_id[17]; /* product id from inquiry */ uchar_t sef_revision[5]; /* revision level from inquiry */ uchar_t sef_scsi_type; /* device type from inquiry */ vsn_t sef_vsn; /* vsn of media that was mounted */ time_t sef_timestamp; /* timestamp of this record */ } The fields of the sef_hdr structure have the following meanings: Field Content sef_magic Has the value SEFMAGIC, as defined in /opt/SUNWsamfs/include/sefvals.h. sef_version Has the value SEFVERSION, as defined in /opt/SUNWsamfs/include/sefvals.h. sef_size The size of this record, excluding the header. sef_eq The equipment number of the device, as configured in the mcf file. For more information, see the mcf(4) man page. sef_devname A character string containing the path name of the device. sef_vendor_id The vendor identification of the device, as obtained from inquiry. sef_product_id The product identification of the device, as obtained from inquiry. sef_revision The revision level of the device, as obtained from inquiry. sef_scsi_type The device type, as obtained from inquiry. sef_vsn Volume Serial Name (VSN) of the volume mounted in the device when the data was generated. sef_timestamp Time that this record as written to the data file. Following the header in each record is some number of log sense pages. Each log sense page consists of a SCSI-standard header followed by triplets of parameter codes, control values, and parameter values. For the exact format of the log sense pages returned by the devices in use at your site, consult the documentation provided with those devices. FILES File Purpose /var/opt/SUNWsamfs/sef/sefdata Contains SEF information. /opt/SUNWsamfs/include/sefvals.h Contains values, such as those for SEFMAGIC and SEFVERSION. /opt/SUNWsamfs/include/sefstructs.h Contains include files for the SEF header, the SCSI-standard header, and other structures. SEE ALSO Sun StorEdge SAM-FS Storage and Archive Management Guide. sefreport(1M), sefsysevent(4). Sun Microsystems Last change: 03 Dec 2001 File Formats sefsysevent(4) NAME sefsysevent - SEF sysevent SYNOPSIS /etc/sysevent/config/SUNW,SUNWsamfs,Device,sysevent.conf AVAILABILITY SUNWsamfs DESCRIPTION In Sun StorEdge SAM-FS and Sun SAM-QFS environments, tape drive SCSI log sense error counter pages 2 and 3 for media analysis are available to the user via a Solaris sysevent. SEF (System Error Facility) sysevents are enabled by default with a default polling interval of once before unload. SEF sysevents behavior is controlled by defaults.conf and samset. How to add a sysevent handler for SEF sysevents: A simple SEF sysevent handler should be executable and may look like this: #!/bin/ksh echo "$@" >> /var/tmp/xx.dat exit 0 To add the SEF sysevent handler to the syseventd(1M): # syseventadm add -vSUNW -pSUNWsamfs -cDevice -sSEF /var/tmp/xx \"\$VENDOR\" \"\$PRODUCT\" \"\$USN\" \"\$REV\" \$TOD \$EQ_ORD \"\$NAME\" \$INQ_TYPE \"\$MEDIA_TYPE\" \"\$VSN\" \$LABEL_TIME \$LP2_PC0 \$LP2_PC1 \$LP2_PC2 \$LP2_PC3 \$LP2_PC4 \$LP2_PC5 \$LP2_PC6 \$LP3_PC0 \$LP3_PC1 \$LP3_PC2 \$LP3_PC3 \$LP3_PC4 \$LP3_PC5 \$LP3_PC6 \$WHERE \$sequence The syseventadm(1M) add command above creates the /etc/sysevent/config/SUNW,SUNWsamfs,Device,sysevent.conf file and a path to your SEF sysevent handler /var/tmp/xx. Note the double quotes are required when using the syseventadm(1M) command because the strings can be empty and the data is positional. To load the SEF sysevent handler: # syseventadm restart SEF sysevent event handler data looks like this: # cat /var/tmp/xx.dat "HP " "Ultrium 2-SCSI " "HUL2M00585" "F45H" 1094048112 82 "/dev/rmt/2cbn" 0x1 "li" "000750" 1091738029 0x0 0x0 0x0 0x0 0x0 0x70b1 0x0 0x0 0x0 0x0 0x322 0x322 0x4645 0x0 0x1 0x282 "HP " "Ultrium 2-SCSI " "HUL2M00617" "F5AH" 1094048116 81 "/dev/rmt/1cbn" 0x1 "li" "NAB975" 1092691221 0x0 0x0 0x0 0x0 0x0 0x35c 0x0 0x0 0x0 0x0 0x0 0x0 0x4a 0x0 0x1 0x283 A C language program to convert time of day $TOD and $LABEL_TIME sysevent macros from digits to text: #include #include #include #include void main(int argc, char **argv) { char str[100]; time_t tm = atol(argv[1]); cftime(str, "%C", &tm); printf("%s0, str); } The complied sefsysevent_time program then can be used to determine the label time of $VSN 000750. # ./sefsysevent_time 1091738029 Thu Aug 5 14:33:49 MDT 2004 To change the default polling cycle from once at unload to once every five minutes use: # samset sef all on 300 # samset device 80: tapealert on and supported, sef not applicable device 81: tapealert on and supported, sef on and supported 300s device 82: tapealert on and supported, sef on and supported 300s device 90: tapealert on and supported, sef on and supported 300s Or use /etc/opt/SUNWsamfs/defaults.conf to change the default behavior: # cat defaults.conf sef=all on 300 The SEF sysevent macros are available in the /opt/SUNWsamfs/include/sefvals.h file. The following is a description of the variables: Field Value Class Device Subclass SEF Vendor SUNW Publisher SUNWsamfs SEF sysevent handler macros about SAM-FS configuration and the SCSI Log Sense Error Counters for pages 2 and 3 and parameters 0-6. Name Value and Data Type VENDOR Inquiry vendor. Data type is string. PRODUCT Inquiry product. Data type is string. REV Inquiry revision. Data type is string. USN Inquiry unit serial number. Data type is string. TOD Time of day. Data type is int32. EQ_ORD mcf file Equipment Ordinal. Data type is int16. NAME Device name. Data type is string. VERSION Inquiry version. Data type is byte. INQ_TYPE Inquiry peripheral device type. Data type is byte. MEDIA_TYPE SAM-FS media type. Data type is string. VSN Volume serial name. Data type is string. LABEL_TIME VSN label timestamp. Data type is integer. SET mcf file Family Set. Data type is string. FSEQ mcf file Family Set Equipment Ordinal. Data type is int16. WHERE SEF location poll=1 or unload=0. Data type is byte. Write log sense page 2: Name Value and Data Type LP2_PC0 Errors corrected without substantial delay. Data type is uint32. LP2_PC1 Errors corrected with possible delays. Data type is uint32. LP2_PC2 Total rewrites. Data type is uint32. LP2_PC3 Total errors corrected. Data type is uint32. LP2_PC4 Total times correction algorithm processed. Data type is uint32. LP2_PC5 Total bytes processed. Data type is uint64. LP2_PC6 Total uncorrected errors. Data type is uint32. Read log sense page 3: Name Value and Data Type LP3_PC0 Errors corrected without substantial delay. Data type is uint32. LP3_PC1 Errors corrected with possible delays. Data type is uint32. LP3_PC2 Total rereads. Data type is uint32. LP3_PC3 Total errors corrected. Data type is uint32. LP3_PC4 Total times correction algorithm processed. Data type is uint32. LP3_PC5 Total bytes processed. Data type is uint64. LP3_PC6 Total uncorrected errors. Data type is uint32. To do simple media analysis, the captured sef data in the /var/tmp/xx.dat file can be formatted for StarOffice spreadsheet analysis and graphing. SEE ALSO samset(1M), defaults.conf(4), sefdata(4), sefreport(1M), tapealert(1M). Sun Microsystems Last change: 18 Oct 2005 4 File Formats stager.cmd(4) NAME stager.cmd - Defines Sun StorEdge SAM-FS or Sun SAM-QFS stager directives SYNOPSIS /etc/opt/SUNWsamfs/stager.cmd AVAILABILITY SUNWsamfs DESCRIPTION Directives for controlling the Sun StorEdge SAM-FS or Sun SAM-QFS stager are read from /etc/opt/SUNWsamfs/stager.cmd. In the stager.cmd file, each directive must appear on its own line. Each directive has the following format: keyword = value Comment lines can appear in the stager.cmd file. A pound sign (#) in column 1 indicates a comment line. The stager.cmd file accepts the following directives: drives = library count Sets the number of drives to use for staging on media library library to a number specified by count. The default value is the actual number of drives in library. The library specified must be the family set name of a media library as defined in the mcf file. If this directive is specified, the stager uses only count number of drives in the media library to stage archive copies. This directive prevents the stager from using all drives in a media library and possibly interfering with archiving. For example, the following directive specifies that 3 drives should be used for staging in an ADIC/Grau media library. drives = gr50 3 bufsize = media buffer_size [ lock ] Sets the stage buffer size for a specific media type. For media, specify a media type from the mcf(4) man page. For buffer_size, specify an integer value in the range 2 < buffer_size < 1024. The default is 4. The buffer_size specified is multiplied by the default block size for media. For more information on default block sizes, see the dev_blksize description on the defaults.conf(4) man page. If lock is specified, the stager locks the stage buffer in memory. If the stage buffer is locked, system CPU time can be reduced. logfile = filename [event] Sets the name of the stager log file to filename, specified as an absolute pathname. By default, no log file is written. event is start, finish, cancel, error, or all. The default is finish, cancel, and error. The stager log file contains a line for each file staged. The line contains the event type, date, time, media, VSN, inode generation number of the file, position and offset of where the file is stored, name of the file, copy number, user id, group id, requestor's user id, equipment ordinal of the drive upon which the file was staged, and the type of stage, 'V' for data verify and '-' for others. maxactive = number Sets the maximum number of stage requests that can be active at one time in the stager to an integer number. The minimum number is 1. The default number is 4000. The maximum number is 500000. The number of outstanding stage requests has a direct impact on incore inode usage, since each request requires an incore inode for the duration of the stage. Sites may wish to increase the default number of incore inodes if they greatly increase the maximum number of stage requests. This can be done by setting ninodes in the /etc/system file, as shown in the following example. set samfs:ninodes=100000 For more information on ninodes, see the Sun StorEdge QFS Configuration and Administration Guide. EXAMPLES The following is an example /etc/opt/SUNWsamfs/stager.cmd file: logfile = /var/opt/SUNWsamfs/log/stager drives= hp30 1 The results of the stager's operations are found in /var/opt/SUNWsamfs/log/stager. For the media library specified as hp30, the stager is allowed to use only 1 drive for staging files. FILES The following files are used by the stager: /etc/opt/SUNWsamfs/stager.cmd Stager command file. SEE ALSO sam-stagerd(1M). defaults.conf(4), mcf(4). Sun Microsystems Last change: 03 Apr 2006