You can use the fts lsft command to display information from both the FLDB and the fileset header for a single fileset. The output from the fts lsft command consists of the output from the fts lsheader command with the -long option followed by the output from the fts lsfldb command. You can indicate the fileset about which information is to be displayed in one of two ways: by specifying the name of a file or directory that is stored in the fileset with the -path option, or by specifying the name or fileset ID number of the fileset with the -fileset option.
Because the fts lsft command retrieves information from the fileset header, you can examine the read-only or backup version of a DCE LFS fileset by adding the .readonly or .backup extension to the name of the fileset specified with the -fileset option or by specifying the ID number of the read-only or backup version. An error message is displayed if the read/write version no longer exists and you fail to specify the .readonly or .backup extension with the name of the fileset.
If multiple read-only replicas of a DCE LFS fileset exist, you can use the -server option to indicate the name of the File Server machine that houses the specific replica to be examined. While all replicas of a fileset are identical by default, indicating a specific replica can be useful if network or hardware problems caused only some of a fileset's replicas to be updated. Omit the -server option to display information about the replica at the fileset's oldest read-only site. The -server option is always unnecessary when the command is used to examine the read/write or backup version of a fileset.
A read-only version of a DCE LFS fileset can exist independently of a read/write version if the fts rmsite command is not used to remove its site when the fts delete command is used to remove the read/write version. A backup version of a DCE LFS fileset can exist independently of a read/write version if the fts delete operation used to remove the read/write version is interrupted before completion; for example, if a system or hardware failure stops a delete operation after the read/write version is removed but before the backup version is removed. (See Removing DCE LFS Filesets for more information about deleting DCE LFS - and non-LFS - filesets.)
Because non-LFS filesets do not have fileset headers, the fts lsft command displays much less fileset header information for non-LFS filesets than it does for DCE LFS filesets.
To display information about a fileset from both its FLDB entry and its fileset header, enter the fts lsft command:
$ fts lsft [{-path {filename | directory_name} | -fileset {name | ID}}] [-server machine]
The -path filename or directory_name option is the name of a file or directory in the fileset. Use the -path option or use the -fileset option to specify the name or ID number of the fileset; omit both options to display information about the fileset that houses the working directory.
The -server machine option names the File Server machine that houses the version of the fileset about which information is to be displayed. This option is useful for examining a particular read-only replica of a DCE LFS fileset for which multiple replicas exist.
Following is an example of the output for this command. The fileset ID number is used to indicate the fileset about which information is to be displayed; the leading 0 (zero) and commas are omitted from the ID number.
$ fts lsft -fileset 196953
_______________________________________________________________
user.terry 0,,196953 RW LFS states 0x10010005 On-line
fs3.abc.com, aggregate lfs1 (ID 10)
Parent 0,,196953 Clone 0,,0 Backup 0,,196955
llBack 0,,0 llFwd 0,,0 Version 0,,25963
429496729 K alloc limit; 1252 K alloc usage
15000 K quota limit; 9340 K quota usage
Creation Fri Oct 15 16:45:16 1993
Last Update Mon Nov 22 11:36:00 1993
user.terry
readWriteID 0,,196953 valid
readOnlyID 0,,196594 invalid
backupID 0,,196595 valid
Minimum local protection level: rpc_c_protect_level_none
Maximum local protection level: rpc_c_protect_level_pkt_privacy
Minimum remote protection level: rpc_c_protect_level_none
Maximum remote protection level: rpc_c_protect_level_pkt_privacy
number of sites: 2
Sched repl: maxAge=2:00:00; failAge=1d0:00:00;
reclaimWait=18:00:00; minRepDelay=0:05:00;
defaultSiteAge=0:30:00
server flags aggr siteAge principal owner
fs3.abc.com RW,BK lfs1 0:00:00 hosts/fs3 <nil>
_______________________________________________________________