Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

2001-07-26 13:41:50 \NODE1.$ZPMON TANDEM.OSS.D40 -00003 $A ,
STATE changed from Stopped to Started because of Operator
Request.
2001-07-26 13:41:50 \NODE1.$ZPMON TANDEM.OSS.D40 -00003 $A ,
STATE changed from Started to Stopped because of Automatic
Unmount by OSS Monitor.
4. When you are unsure of the effect of an action on a fileset, use the STATUS FILESET command
DETAIL option to obtain the last internally reported error information for it. Look up that error
in “Numbered Messages” (page 361).
For example, this dialog illustrates the condition of the fileset:
STATUS FILESET FILESET01, DETAIL
OSS Detailed Status FILESET \PIMA.FILESET01
State.................. STOPPED
MountTime..............
LastError.............. 9
ErrorDetail............ 0
ErrorTime.............. 26 Jul 2001, 13:41:50.392
FsckName...............
NumVols................ 2
Volumes:
$DATA01 $DATA02
The LastError value reported (9) indicates that confusion exists over the state of the mount
point. In this example, the LastError value is the same as the OSS Monitor error message
number (E0009).
Managing and Repairing Fileset Catalog Files
An OSS name server maintains a catalog file for each fileset it manages. These catalog files require
maintenance when:
• New OSS features require changes to the format of entries in the catalog. This maintenance
is described in “Upgrading OSS Catalog Files” (page 170).
• Old catalog files need to be moved or removed as part of fileset management. This maintenance
is described in “Moving and Removing OSS Catalog Files” (page 171).
Upgrading OSS Catalog Files
In most cases, a fileset created while your site used a previous version of Open System Services
can be used unmodified with the current software. Version 1 fileset catalog files are not supported
on systems running J-series RVUs, H06.08 and later H-series RVUs, or G06.29 and later G-series
RVUs. Your Version 1 fileset catalog files should have been automatically upgraded to Version 2
when you installed the T8622G10 version of the OSS Monitor and started it for the first time. If
your fileset catalog files were not upgraded at that time, upgrade them as soon as possible.
Filesets with catalog files that are not upgraded to the current RVU cannot support OSS features
available in the current RVU but not available when the fileset was created or last upgraded. For
example:
• A fileset created on a system running a D3x RVU (a Version 1 catalog fileset) cannot contain
symbolic links until its catalog file is upgraded to a Version 2 or a Version 3 catalog fileset.
(Version 3 catalog filesets are supported on systems running J06.03 and later J-series RVUs,
H06.08 and later H-series RVUs, or G06.29 or later G-series RVUs only.)
• A fileset created on a system running a D4x RVU or a G-series RVU before G06.29 cannot
contain access control lists (ACLs) until its catalog file is upgraded to a Version 3 catalog
fileset. Version 3 catalog filesets are supported on systems running J06.03 and later J-series
RVUs, H06.08 and later H-series RVUs, or G06.29 or later G-series RVUs only. New filesets
170 Managing Filesets