Technical data

NFS Server
20.10 Maintaining a Container File System
20.10.5 Deleting a Container File System
You can delete a container file system with all its directories and files by issuing
the DELETE CONTAINER command. For example, to delete the UNIX container
created on WORK1$:[GROUP_A], enter the following command:
TCPIP> DELETE CONTAINER WORK1$:[GROUP_A]
Use the UNMAP command to unmap the container file system before you delete
it.
20.10.6 Verifying the Integrity of a Container File System
You may want to verify the integrity of your container file system under the
following circumstances:
• If you are experiencing disk read or write errors or encountering problems
backing up the container.
• If you are making copies or restoring files from a backup.
The container file records the volume label and the Files–11 file identifiers of
the actual files on the disk. If you copy the file system or change the volume
label, you must run ANALYZE CONTAINER/REPAIR after you copy the files
so that the file identifiers and volume label are corrected for the new location
of the files.
• During system startup after a system failure.
You can use the ANALYZE CONTAINER command to check the integrity of
your container file system. This command is similar in function to the DCL
ANALYZE/DISK_STRUCTURE command.
Before analyzing the container file system, unmap it to prevent access to it during
the analysis.
Note
The underlying OpenVMS file system must be mapped before you use the
ANALYZE CONTAINER command.
For example, to verify the integrity of a container file system called /GroupA
located in WORK1$:[GROUP_A], enter the following commands:
TCPIP> UNMAP "/GroupA"
TCPIP> MAP "/group_a" WORK1$:
TCPIP> ANALYZE CONTAINER WORK1$:[GROUP_A]
File system access to the container file is suspended while the container is being
analyzed.
Table 20–2 lists the components of a container file system that are normally
verified by the ANALYZE CONTAINER command.
NFS Server 20–15