We're having a difference of opinion over certain toaster behavior and whether it is desirable or not. The specific issue is CIFS file locking.
We use out 630 for building design software. We have a QA-like group who are sort of the front line sof testing. Their goal is to test software as fast as we get it built, so they test our actual build area. If someone opens up one of our applications, the NAC keeps all related libraries, execs, and datafiles locked until the application is exited.
This of course prevents us from changing data that is in-use, a behavior I see as desirable. However, it also can cause the build group (my group) heartache because we can't patch a given file if it's in use, which some see as an 'unintended feature'.
Is this indeed proper bahavior? If so, is there a "Big Hammer" mode we can use to break locks if needed?
-Jeff
If someone opens up one of our applications, the NAC keeps all related libraries, execs, and datafiles locked until the application is exited.
Our goal is to match the CIFS behavior of an NT server as closely as possible. Do you see a difference between NetApp and NT in this area?
Of course, where NFS and CIFS interact, there is no model to emulate exactly, but for CIFS-only interactions, NT is the target behavior.
Dave
-
hitz＠netapp.com -
Jeff Stampes