Prerequisite: The VOB being activated must already have a VOB tag for your host's network region in the ClearCase registry. See the mkvob and mktag reference pages.
The mount command activates one or more VOBs on the local host. The mount command mounts a VOB as a file system of type MVFS (multiversion file system) and is inapplicable to non-MVFS installations.
Mounting All VOBs
The mount –all command mounts all public VOBs listed for your host's network region in the VOB registry. (It does not mount private VOBs or VOBs whose tag entries include the mount option noauto.) On UNIX systems, this command executes at ClearCase startup time; see the init_ccase reference page.
UNIX—Mounting of Public and Private VOBs
A public VOB can be activated by any user; if the mount-over directory does not already exist, it is created.
A private VOB can be activated only by its owner. The root user or VOB owner can use the standard mount(1M) command to mount a private VOB; other users cannot mount it. The mount-over directory must already exist and be owned by the VOB owner.
Windows—Mounting of Public and Private VOBs
A public VOB can be activated with the following command:
Usually, the system administrator automates this command for ClearCase users at login time.
Any user can mount any VOB, public or private. The private designation means only that a VOB must be mounted separately, by name.
VOB Tags and the VOB Storage Registry
You reference a VOB by its VOB tag (the full pathname of its mount point), not by its storage area pathname. The mount command uses the VOB tag to retrieve all necessary information from the ClearCase registry: pathname of VOB storage area, pathname of mount point, and mount options.
OPTIONS AND ARGUMENTS
Making a Mount Persistent
Specifying Mount Options
- Mounts each VOB using the –options field
in its VOB tag registry file.
- –opt·ions mount-options
- Ignores the –options field
in the VOB tag registry file entry and uses the specified set of options,
which can include these:
All platforms—ro, rw, soft, hard, intr, nointr, timeo, retrans, noauto, nodnlc, noac, acdirmin, acdirmax, acregmin, acregmax, actimeo
UNIX—nodev, nosuid, suid
Windows— suid (applicable only for a tag used to mount a VOB on UNIX), poolmap
Note: On UNIX, see the appropriate operating system reference page (for example, mount(1M)) for a description of these options. Enclose this argument in quotes if it contains white space.
Note: On UNIX, if you don't specify a time-out or retransmission option, default values are used:
Note: On UNIX, by default, a VOB is mounted in nointr mode. This means that operations on MVFS files (for example, open(2)) cannot be interrupted by typing the INTR character (typically, CTRL+C ). To enable keyboard interrupts of such operations, use the intr mount option.
Note: On Windows, use commas to separate multiple options, not commas and white space. Options that take numeric arguments take the form option=n. Enclose the entire option list in quotes if it contains white space.
Note: The time-out values specified in several of these mount options affect the view's metadata latency (the delay before changes to VOB metadata become visible in a dynamic view other than the one in which the changes were made). Longer time-out values improve performance at the expense of greater latency. Shorter time out values decrease latency, but also have an impact on view performance because the caches must be refreshed more frequently.
Specifying the VOBs
- Mounts the VOB with this VOB-tag,
which must be specified exactly as it appears in the vob_tag registry
file. Use lsvob to list VOBs.
- (Mutually exclusive with –options)
Mounts all public VOBs listed for your host's network region in the VOB registry,
using the mount options in their VOB tag registry entries. (Including the
mount option noauto in a VOB tag's registry entry prevents
the VOB from being mounted by mount –all.)
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.