NAS Tutorial: Oplocks and NASes - SmallNetBuilder https://www.smallnetbuilder.com/nas/nas-features/30039-nas-tutorial-op...

NAS Tutorial: Oplocks and NASes Check out the new Wi-Fi System Charts, Ranker and
Finder!
Published: Thursday, 31 May 2007 05:40
Written by Tim Higgins

Tags: NAS oplock

Share 0 Tweet Share

-12%
Background

Start Prev 1 2 Next End

Background

Most Read This Week

Wi-Fi System Roundup

Ubiquiti AC Pro and AC Lite Access Points Reviewed
AC1900 First Look: NETGEAR R7000 & ASUS RT-AC68U
ASUS ROG Rapture GT-AC5300 Wireless-AC5300 Tri-Band Gaming Router
Reviewed

I recently learned something about NASes that buyers looking to use these products for database and other simultaneous-file- NETGEAR R7000P Nighthawk Smart WiFi Router with MU-MIMO Reviewed
access applications should know about. The issue is how Opportunistic Locking ("oplocks") are handled.
For those who are unfamiliar with oplocks, this excerpt from a SuperBase article explains:
Opportunistic locks (oplocks) are a characteristic of theLAN Manager networking protocol implemented in the 32-
Bit Windows family of operating system environments. Bascially, oplocks are guarantees made by a server for a Top Ranked Routers
shared logical volume to its clients. These guarantees inform the Client that a file's content will not be allowed to
be changed by the server, or if some change is imminent, the client will be notified before the change is allowed to
proceed.

Note that oplocks are part of the SMB/CIFS protocol, so don't apply to systems using AFP, NFS or other networked filesystem
protocols. But as part of SMB/CIFS, oplocks are implemented in Samba, the open source re-implementation of SMB/CIFS used
by all Linux-based NASes. AC AC DWS
I also checked with filesystem expert Don Capps, creator of iozone, which I use for all NAS testing. Don had the following See More Rankings
comments on oplocks (which I've lightly edited):
Support Us!
Oplocks are on by default in all Windows clients and servers. The purpose
is to enable the client to perform a locking operation and write data to a file.
If you like what we do and want to thank us, just buy something on Amazon. We'll get a
As long as no one else is touching the file, the lock operation happens on
small commission on anything you buy. Thanks!
the remote client and no one is the wiser. This is a huge performance win.
However, if multiple clients are trying to read or write to the same file, then
oplocks is a huge performance loser. The problem is that the first client
gets the oplock granted by the server and begins work. Then up comes the
second client. The server sees the possible conflict and sends a Revoke Arduino Project Builder
lock operation to the first client and lets both of them know that oplock
Control sensors, motors &
requests will not work on this file due to multiple concurrent clients trying to actuators. Drag & drop project
access it. As this point all locking operations are sent to, and handled by, builder. Free download.
the server.
SO... We can generalize here. If there exists any file that is going to be shared by multiple clients then it would be
a really good idea to disable oplocks on the clients, or the server. This would eliminate the lock revocation from
the system, and would eliminate extra overhead that is associated with oplocks. Note that the entire discussion of
when to use, and when not to use oplocks is discussed in most Samba books.

Don goes on to offer the following suggestions (bolding is mine):

1. If a system (clients and server) will be used to perform shared file operations, then oplocks should be disabled.
2. If a system will be used to perform non-shared operations, then oplocks is a huge performance win, and should
be enabled.
3. If a system will be used for both shared and non-shared file accesses, then the exported shares with the
shared files should have oplocks disabled, and all other shares should have oplocks enabled.
4. If anyone tells you to set all oplocks on, or off for a general purpose (shared, and non-shared files) system,
then this person is either being silly, or does not understand oplocks, and their proper usage.

Discuss this in the Forums

Background

Start Prev 1 2 Next End

-100% -12%

More NAS

SYNOLOGY DS1817 QNAP TS-453B SYNOLOGY QNAP TS-431P

DISKSTATION QUAD-CORE DS1517+ SOHO NAS
REVIEWED MULTIMEDIA NAS DISKSTATION REVIEWED
REVIEWED REVIEWED

2 of 3 8/17/17, 10:59 PM