Removes a specified read/write or backup version of a DCE LFS fileset
Synopsis
fts delete -fileset {name |ID} -server machine -aggregate name
[-cell cellname] [{-noauth |
-localauth}] [-verbose] [-help]
Options
-fileset {name | ID}
Specifies the complete name or fileset ID number of the read/write or backup fileset to be removed. Include the .backup
extension if specifying the name of a backup fileset.
-server machine
Names the File Server machine from which to remove the fileset. Specify the File Server machine using the machine's DCE path name, the machine's host
name, or the machine's IP address.
-aggregate name
Specifies the device name, aggregate name, or aggregate ID of the aggregate from which to remove the fileset. These identifiers are specified in the
first, second, and fourth fields of the entry for the aggregate in the dcelocal/var/dfs/dfstab file.
-cell cellname
Specifies the cell where the command is to be run. The default is the local cell of the issuer of the command.
-noauth
Directs fts to use the unprivileged identity nobody as the identity of the issuer of the command. If you use this option, do not use the
-localauth option.
-localauth
Directs fts to use the DFS server principal name of the machine on which the command is issued as the identity of the issuer. Use this option only if the
command is issued from a DFS server machine (a machine that has a DFS server principal in the local Registry Database). You must be logged into the server machine as root for this option to
work. If you use this option, do not use the -noauth option.
-verbose
Directs fts to provide detailed information about its actions as it executes the command.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The fts delete command removes the read/write or backup DCE LFS fileset indicated by the -fileset option from the site specified by the
-server and -aggregate options. Versions of the fileset are removed and the Fileset Location Database (FLDB) entry for the fileset updated to record the removals as follows:
· Removing a read/write fileset automatically removes its associated backup version (if the backup version exists). If read-only versions of the fileset exist, site information for the read/write and backup versions of the fileset is removed from the fileset's FLDB entry and the status flags for both versions are set to invalid (their fileset ID numbers are still recorded), but the read-only versions of the fileset are not affected. If no read-only versions of the fileset exist, the entire entry for the fileset is removed from the FLDB.
· Removing a backup fileset removes site information for the backup version from the fileset's FLDB entry and marks the backup version as invalid but does not erase its fileset ID number. Read/write and read-only versions of the fileset are not affected.
The number of fileset entries recorded in the server entry in the FLDB for the File Server machine from which a read/write or backup version of a fileset is removed is decremented once for each deleted version of the fileset. (Note that, if the indicated version of a fileset does not exist at the specified site but is referenced in the fileset's FLDB entry, the command removes site information about that version of the fileset from the fileset's entry and generally performs all other operations as indicated.)
Before you remove the read/write (and backup) version of a fileset, use the fts rmsite command to remove the fileset's replication sites and to instruct the Replication Server to remove the replicas stored at the sites. If Release Replication was used for the fileset, use the fts rmsite command to remove the replication site and replica stored at the read/write fileset's site as well.
After removing a fileset, use the fts delmount command to remove its mount point. Note that it might be better in some cases to remove a fileset's mount point before deleting the fileset; removing the mount point first ensures that no users are accessing the fileset when it is deleted.
If the DCE LFS fileset to be removed is also mounted locally (as a file system on its File Server machine), you must remove its local mount point before you delete it; the fts delete command cannot be used to delete a fileset that is mounted locally. In addition, because the backup version of a fileset is removed when its read/write version is removed, you cannot remove the read/write version of a fileset if its backup version is mounted locally. You must remove the backup version's local mount point before deleting the read/write version.
The fts delfldbentry command can be used to remove an FLDB entry for a fileset. Use the command only when you are certain that a fileset deletion was not recorded in the FLDB. The fts zap command can be used to remove a fileset when it is urgent that the fileset be removed but the FLDB is inaccessible. When the FLDB is again accessible, use the fts delfldbentry command to remove the fileset's FLDB entry or use the fts syncfldb and fts syncserv commands to synchronize the FLDB with the state of the filesets.
The fts delfldbentry command is also used to remove the FLDB entry for a non-LFS fileset. The fts delmount command is then used to remove its mount point, and the dfsexport command is used to detach the partition it resides on from the global namespace.
Privilege Required
The issuer must be listed in the admin.ft file on the machine specified by -server. The issuer must also be listed in the admin.fl
files on all Fileset Database machines or own the server entry for each machine on which a version of the fileset to be deleted resides.
Examples
The following command deletes the read/write fileset named user.terry and its backup version (if it exists) from the aggregate named /dev/lv01 on the
File Server machine named fs3:
$ fts delete user.terry /.../abc.com/hosts/fs3 /dev/lv01
Related Information
Commands: dfsexport(8dfs)
Files: dfstab(4dfs)