samba - Jan 2004 - using VSS on a samba server - no smb locks ?

Hi all,

We are considering moving our VSS database from a Win2K server to a samba
server.
All clients are Win2K clients.

I used the VSS tool "testlock.exe" to make sure the native lock mode
can be used.
The test was successful, and I saw that an SMBlock transaction was performed,
and a reply_lockingX was replied.

When I opened a VSS database on the samba server and started to use it - I saw
no SMBlock operations.

Doesn't make sence to me, because some kind of locking must be done.

Any ideas ?

Thanks,
Nir

On Fri, Jan 30, 2004 at 03:08:21PM +0200, Nir Livni
wrote:
> Hi all,
> 
> We are considering moving our VSS database from a Win2K server to a samba
server.
> All clients are Win2K clients.
> 
> I used the VSS tool "testlock.exe" to make sure the native lock
mode can be used.
> The test was successful, and I saw that an SMBlock transaction was
performed, and a reply_lockingX was replied.
> 
> When I opened a VSS database on the samba server and started to use it - I
saw no SMBlock operations.
> 
> Doesn't make sence to me, because some kind of locking must be done.
Did you only test with one user ? Is so, an oplock will cause
no locking attempts to be seen on the wire (the client redirector
optimises them out when it has  an oplock).

Jeremy.

----- Original Message ----- 
From: "Jeremy Allison" <jra@samba.org>
To: "Nir Livni" <nir.livni@cyber-ark.com>
Cc: "Jeremy Allison" <jra@samba.org>;
<samba@lists.samba.org>
Sent: Friday, January 30, 2004 10:25 PM
Subject: Re: [Samba] using VSS on a samba server - no smb locks ?

> On Fri, Jan 30, 2004 at 10:13:55PM +0200, Nir Livni wrote:
> >
> > Well, actually all oplocks where turned off in my smb.conf.
> > I tried to checkin and checkout some files with few users, but no
SMBlocks.
> > Using samba-2.2.8a (I forgot to mention)
>
> No lockingX calls ? There are several possible locking calls. Or
> maybe the app does some higher level synchronisation.
>
VSS has a "lock_mode" parameter, that has two modes. Native /
FileLock.
Both of them achieve the same result - locking database files for
synchronization.

The "testlock" utility was ment to help administrators to deteremine
whether
their file system supports the Native lock mode. If the test fails - they
have to use FileLock lockmode.

Testlock generates a lockingX transaction (are there any other smb locking
transactions ?), which means that the lockingX is the way to get a native
lock in VSS.
FileLock lock mode simply creates files (.lck) in the "locks" folder
of the
database, to mark locks. When the file is deleted - lock is removed.

I am not saying that there is a samba problem here.
I just think that the fact that testlock.exe uses lockingX, but the clients
of VSS do not use lockingX, show that there may be a configuration problem,
which I am trying to solve.

Nir
> Jeremy.