Log files filling up Quorum drive
Michelle Weber
brought down the entire cluster 3 times now - twice this week.
The cache file that is saved to the root of our Q drive is regularly growing
to fill up the entire quorum drive. Once it fills up, the entire cluster
dies.
How can we prevent this file from growing so large? Is something wrong
that's causing this? We read that the Q drive should be about 500mb to
accommodate for about 10mb of files. We made the drive 1gb just to be extra
safe.
I temporarily fix the problem by deleting this file, and rebuilding the log
(full details below). The servers then run without the cache file and
eventually it gets rebuilt and then starts growing and growing.
Config:
* Two identically configured servers (HP Proliant)
* Both running Windows 2000 Advanced Server
* Clustered Services: SQL Server 2000, file/print sharing
* Quorum drive (Q:) is 1gb partition with nothing else on it
Any ideas??
To fix the problem here's what we do (May be useful to other readers), but
it only fixes the problem temporarily until the file fills up again.
* Shut down all but one of your cluster servers (In our case we only have
2). It is EXTREMELY important to leave all servers off while you do this, to
avoid further corruption of the Q drive.
* On the remaining server:
* Disable the cluster service
* Disable the cluster disk driver in Device Manager by changing the driver
to "DISABLED" (Note: this is a hidden device. Go to the View menu to see
hidden devices. Most documentation skips this point.)
* Restart the server you made these changes to
* Delete the over-grown cache file
* Set the Cluster disk driver back to "SYSTEM".
* Restart the server
* In the services control panel start the cluster service manually with the
"-resetquorumlog" parameter
* At this point your clustered services should be running normally.
* Turn on the other cluster servers
Any assistance would be greatly appreciated!
--
Michelle Weber
mich...@pliner.com
Pliner Solutions, Inc
http://www.pliner.com
Tel: 215-658-1601
Fax: 215-658-1602
John Toner
"cache" file. It certainly isn't MSCS. What is the name of the file that's
filling your drive? While things are running, you might be able to use
certain tools...like handle.exe from sysinternals...to figure out which
application has a thread to this cache file.
As for your procedure...that's a bit extreme, but obviously it works for
you. If you start the cluster service with the -noquorumlogging flag, then
you should be able to go and delete the unnecessary files on your Q: drive.
Once complete, stop and restart the cluster service with no flags.
Regards,
John
"Michelle Weber" <mich...@pliner.com> wrote in message
news:On68Laq5...@TK2MSFTNGP12.phx.gbl...
Thomas Solkod
- open clusteradminstrator
- right click on cluster name
- look at tab quorum for cluster log size
Thomas