samba - May 2002 - kernel oplocks don't work on Linux/Alpha

Hello,

I have a Compaq Alpha server with Linux 2.4.18 and samba 2.2.4 and NT-clients.

After accessing a file from a NT-client this file cannot be accessed on the
Linux side for a while.

Creating the file on the server:
    echo test >file

on the NT-client (gives "test"):
    TYPE file

try to access it on the server:
    cat test
cat: file: Invalid argument

After waiting approx. 40 sec. it succeeds.


This problem does not occur with "kernel oplocks=no", but file
contents are not consistent then.

The same configuration on an Intel server (2.4.16, samba 2.2.3a) works.

Markus.
-------------- next part --------------
HTML attachment scrubbed and removed

On Fri, 3 May 2002, Dr. Markus Ammer, Ingenieurb?ro Ammer wrote:
> Hello,
> 
> I have a Compaq Alpha server with Linux 2.4.18 and samba 2.2.4 and
> NT-clients.
> 
> After accessing a file from a NT-client this file cannot be accessed on
> the Linux side for a while.
> 
> Creating the file on the server:
>     echo test >file
> 
> on the NT-client (gives "test"):
>     TYPE file
> 
> try to access it on the server:
>     cat test
> cat: file: Invalid argument
> 
> After waiting approx. 40 sec. it succeeds.
> 
> 
> This problem does not occur with "kernel oplocks=no", but file
contents
> are not consistent then.
> 
> The same configuration on an Intel server (2.4.16, samba 2.2.3a) works.
You'll probably have to bring this up with the linux-kernel mailing list.
Not sure who is maintaining that code in the kernel now.












cheers, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN
0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--