You can use the mvfsstorage command to find
container files for versions, derived objects, and view-private files.
About this task
The data containers for all MVFS files are stored within a VOB or view storage directory, as
shown in the following
table.
Table 1. Storage directories for MVFS filesKind of file |
Storage directory |
Version (checked-in) |
VOB source storage pool (s subdirectory of the VOB storage
directory). |
Checked-out version |
View-private data storage (.s subdirectory of the view
storage directory) |
Unshared or nonshareable derived object |
View-private data storage (.s subdirectory of the view
storage directory) |
Shared derived object |
VOB derived object storage pool (d subdirectory of the VOB
storage directory) |
View-private file |
View-private data storage (.s subdirectory of the view
storage directory) |
The following examples show how the ccase-home-dir/etc/mvfsstorage utility locates the physical storage for an MVFS file.
Procedure
- Locating a checked-out version. This example shows the
location in view-private data storage of the checked-out version of text_file element cmd.c:
mvfsstorage cmd.c
\\phobos\vw_store\arb.vws\.s\00050\8000000B.00B0.cmd.c
- Locating a checked-in version's cleartext container. For
a checked-in version of an element that uses a single data container to store
all its versions, mvfsstorage shows the location of the
cleartext data container into which the type manager places the version.
mvfsstorage cmd.c@@\main\1
\\sol\vobstore\monet.vbs\c\cdft\28\32\8a1a9a50010e11cca2ca080069021822mvfsstorage cmd.c@@\main\2
\\sol\vobstore\monet.vbs\c\cdft\3a\33\8e4a9a54010e11cca2ca080069021822
- Locating a checked-in version’s source container. For
a checked-in version of an element that uses a separate data container for
each version, mvfsstorage shows the location of the data
container in the source pool:
mvfsstorage monet.icon
\\sol\vobstore\monet.vbs\s\sdft\26\4\474fa2f4021e11cca42f0800690605d8
Element
types that store each version in a separate container do not use the cleartext
pool. Instead, programs access the data container in the source pool.
- Locating a view-private file. As with a checked-out
version, a view-private file is located in a view’s private data storage:
mvfsstorage ralph_msg
\\sol\view_store\arb.vws\.s\00050\8000000C.00BD.ralph_msg
- Issues with remote pools. On computers that runs Linux or the UNIX system, VOB storage pools can be located outside the VOB storage
directory itself; likewise, a view’s private storage area can be located outside the view storage
directory. If mvfsstorage indicates that a data container is in a nondefault VOB
storage pool, use the lspool command to determine the location of the pool. The
default pools are sdft (default source pool), cdft
(default cleartext pool), and ddft (default derived object pool). For example:
ccase-home-dir/etc/mvfsstorage hello.h
/vobstore/monet.vbs/c/clrtxt.1/36/f/6b6ed22b08da11cca0ef0800690605d8
cleartool lspool –l clrtxt.1
pool "clrtxt.1"
08-Feb-93.10:25:46 by (vobadm.vobadm@starfield)
"nonlocal cleartext storage for monet VOB"
kind: cleartext pool
pool storage remote host:path "sol:/netwide/public/ccase_pools/clrtxt.1"
pool storage local pathname "/vobstore/monet.vbs/c/clrtxt.1"
maximum size: 0 reclaim size: 0 age: 96
clrtxt.1
is a nondefault cleartext pool. Use the ls command to determine whether a view’s
private storage area (subdirectory .s) is local:
ls –ld ~jones/view_store/temp.vws/.s
lrwxrwxr-x 1 jones dvt 34 Feb 17 17:06
/usr/people/jones/view_store/temp.vws/.s -> /public/jones_temp
- Links and directories on Linux and the UNIX system. mvfsstorage deals with VOB and file-system link and directory
objects as follows:
- For a link, mvfsstorage indicates the storage directory of the object to
which the link points. This applies to all links: view-private hard links and symbolic links, VOB
hard links, and VOB symbolic links.
- A view-private directory does not have a data container; nor does a directory element. In both
cases, mvfsstorage displays the directory pathname.