🚀 go-pugleaf

In article <1992Jul30.004447.1273@iitmax.iit.edu>, draughn@iitmax.iit.edu (Mark Draughn) writes:
|>I'm having a system performance problem that I hope someone can help
|>me with.
|>
|>We're running VMS 5.4-2.
|>
|>We have about 9000 users on our VAX cluster.  All of the user
|>directories are on one volume set containing about 200000 files using
|>2.5 GB, which is served to the cluster.
|>
|>THE PROBLEM:  After a crash, when the volume set is mounted, the
|>automatic rebuild takes about an hour.  This is a major pain.
|>
|>I've got things set up so that this volume is only rebuilt if the
|>server crashes.  If one of the satellites crashs, we live with the
|>corruption.  This is still a problem because a server crash will hang
|>all user file activity for an hour during the rebuild.  Even a simple
|>shutdown-and-reboot cycle on the server can take an hour if any of the
|>systems in the cluster has crashed since the last reboot.

If your crashes aren't very frequent, why not skip the rebuild until
a slack period like midnight?

	$ MOUNT/NOREBUILD ...

Then a batch job can do:

	$ SET VOLUME/REBUILD ...

--
Reece R. Pollack
Senior Software Engineer
The Wollongong Group, Inc.