Hi Matt,
No we haven't tried 5.2.2P1 or 5.3 yet to solve the oplock bug. The reason is that out filer is stable at the moment and we have found in the past that we end up with some stability problems when we install another release of OnTap. We have a workaround for the oplocks bug which doesn't bite us so hard at the moment
(Having said that we will be upgrading to 5.3 sometime as NTP would be nice)
GB
From: Matt Day[SMTP:mday@netapp.com] Sent: 31 July 1999 00:21 To: Garrett Burke Cc: toasters@mathworks.com Subject: Re: CIFS Remote Backup Options
c) oplocks. This has caused us numerous problems. We now run the
backups
with oplocks turned off, as there some sort of interaction between
ARCServe
and the oplock code (we tried a few D releases but never got around it) which means that things run very, very slowly. Like, 2 days to run the backup!
Hi Garrett,
There is an oplock bug in 5.2.1 (burt12483) that sometimes delays the delivery of oplock break messages -- I bet that's the performance problem you're hitting with oplocks enabled. The fix for this bug is available in 5.2.2P1 and 5.3. Have you tried either of those releases?
Matt
-
Garrett Burke