Lucent Technologies 585-210-940 User Manual
Maintaining Mirrored Systems
CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Repairing or rebuilding the /cms file system
46
The system prompt should return without error, as shown above. (Of
course, file and block counts in the last line will vary.) In that case,
continue with the next step.
course, file and block counts in the last line will vary.) In that case,
continue with the next step.
If you get an error message, however, repeat the
fsck
command. If
the command still returns errors after 10 repetitions, stop this
procedure and skip ahead to “Rebuilding /cms,” below.
procedure and skip ahead to “Rebuilding /cms,” below.
Continue with step 6 only if you entered the fsck command and
it returned the system prompt without error messages.
it returned the system prompt without error messages.
5. This step remounts
/cms and reallocates the swap file. How that is
done depends upon whether you altered the
vfstab file earlier in this
procedure.
If you altered the
vfstab file earlier (step 4), do the following:
a. Load the
/etc/vfstab file into your editor.
b. Find the
#/cms
line. Uncomment the line. (To uncomment a
line, delete the initial pound sign.)
c. Save the file and exit the editor.
d. Reboot by entering the following command:
If you did NOT alter the
vfstab file, do the following:
a. Remount
/cms:
6. Turn on CMS:
a. Enter a
cmsadm
or
cmssvc
command.
b. Select the
run_cms
option.
c. Select the
Turn on CMS
option.
The file system has now been repaired and should be operating normally.
If this procedure completed successfully, do NOT do the “Rebuild
/cms” procedure.
/cms” procedure.
Rebuilding
/cms
3
Do this procedure only if you have tried the fsck command at least
ten times and it is still returning errors.
ten times and it is still returning errors.
If you are running a
Sun Enterprise 3500 platform, do not begin this
procedure until you have checked the
/kernel/drv/st.conf file to make sure
the 3500’s 8mm tape drive is properly defined. See
for details.
To complete this procedure, you need the latest CMSADM backup. Also,
/cms should still be unmounted at this point. If anything has been done to
alter that, repeat steps 2 through 4 of the “Repairing /cms” procedure.
/cms should still be unmounted at this point. If anything has been done to
alter that, repeat steps 2 through 4 of the “Repairing /cms” procedure.
#
/usr/sbin/shutdown
-i6
-g0
-y
#
mount
/cms