write-cache enabled on server drive (Networking Products)
At 17 FEB 2010 11:39:44AM dave w bennett wrote:
We have a client which is receiving FS1009 and FS102 errors once or twice a week on different workstations and both these messages always state that a REV file is read-only which is not true. The user will escape from the error and get kicked out of AREV and log back in and can perform the same save without any issues. They are using the 2.1 driver on a Windows 2003 server with XP workstations. Back in the day we had to have write-cache disabled, is that still the case with the 2.1 driver?
Dave
At 18 FEB 2010 06:04AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
We always recommend this for all workstations - we have seen aberrant behaviour with Windows caching updates without it.
World leaders in all things RevSoft
At 18 FEB 2010 09:14AM Jared Bratu wrote:
Verify that the service is being used by the workstations on all of the data directories. Its possible one of the REVPARAM files is mis-configured or the client(s) aren't able to communicate with the server when attaching to certain data directories. If the client can't communicate with the server as specified in the REVPARAM file then it would slip into local mode and write-cache would be an issue. However, if the service is in use write-caching shouldn't be an issue.
The Universal Driver includes a management tool to list who is connected to the server linear hash service. The All Networks driver isn't supported and doesn't have this tool. Instead you can verify operation of the service by opening the "Opened Files" list from the server. If any of the clients have locks on .LK or .OV files then the service was bypassed and the clients are accessing the files directly (not optimum configuration).
You must check for locks while the application is active and in use. What does the opened files list show?
At 18 FEB 2010 04:31PM dave w bennett wrote:
We have confirmed that every REVPARAM file has the same setting of serveronly=true
We have confirmed that the SCSI drive on the server has write-cache checked as on, do we need to uncheck this setting when using the 2.1 driver?
Dave
At 20 FEB 2010 10:01PM Richard Bright wrote:
Dave,
I believe that Sprez referred to disabling write-caching on each CLIENT workstation. Write-cache on the Server SCSI drive is quite separate issue.
Client workstation caching delivers a percieved performance improvement for activities such as document processing; it is a liability in a shared database environment in which multiple users may be accessing common records.
Richard Bright
BrightIdeas New Zealand