samba - Aug 2007 - Samba on Debian with shares on nfs-filesystem

Hello,

Actually I have some troubels concerning samba (3.0.24) on debian (4.0):

I would like to have some samba-shares on a nfs-filesystem.

NFS works fine for the Linux clients and the Linux server. The nfs 
filesystem is mounted from an other server on /home.

The next step is to set up samba to have some shares on the nfs Filesystem 
(/home/$LOGIN, anonymized configuration attached).
Connecting to the samba shares works for Linux and Windows clients fine. 
Downloading files also does fine.
Copying files from the local filesystem to the samba-shares works fine for 
Linux-clients (via smb!), but not for Windows clients:
Copying files from Windows 2k to the samba share results in the following 
error message:

foo kann nicht kopiert werden: Der Prozess kann nicht auf die Datei 
zugreifen, da ein anderer Prozess einen Teil der Datei gesperrt hat.
(In english something like:
Can't copy foo: process cannot acces the file as some other file is 
locking a part of the file.)

But there is no other process accessing this file.

Applications can "save" their files to the samba shares. These files
have
the filesized as wished by the windows-application but are filled with 
zeros.

According to http://www.debianforum.de/forum/viewtopic.php?t=83647 I am 
not alone with this problem. Further:
The member of that forum wrote that he had compiled several samba verisons 
by himself on debian 4.0/etch:
The problem did not occur with samba 3.0.22 and 3.0.23. But the problem 
occured also on the "self-compiled" samba 3.0.24.

He also compiled several versions of samba on debian 3.1/sarge:
There the problem did not occour with any version of samba.

I have tried to have these samba-shares on nfs3 and nfs4 filesystems. The 
choice of nfs3 or nfs4 doesn't affect the problem.

So my question is how it is possible to use samba on debian 4.0 in such a 
configuration.
I would prefer to use official debian packages or the packges from the 
samba.org-webpage (but at the moment there are no Debianpackages for 
Debian 4.0 on the samba Webpage).
I could compile samba by myself, but I would prefer some other solution.

Thanks and best regards
Thomas
------------
PS: As I don't know wheter it is a samba issue or only a debian issue, 
I "crosspost" to both mailinglists. 
-- 
Thomas Flaig
mailto: thomas.flaig@unibw.de
-------------- next part --------------
[global]
	workgroup = $WORKGROUPNAME
	server string = %h server
	interfaces = $IPs
	bind interfaces only = Yes
	obey pam restrictions = Yes
	passdb backend = tdbsam
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:*
%n\n *password\supdated\ssuccessfully* .
	log level = 2
	syslog = 0
	log file = /var/log/samba/log.%m
	max log size = 1000
	printcap name = cups
	logon path = \\$HOSTNAME\%U\profile
	logon drive = H:
	logon home = \\$HOSTNAME\%U
	domain logons = Yes
	os level = 240
	preferred master = Yes
	domain master = Yes
	dns proxy = No
	wins support = Yes
	panic action = /usr/share/samba/panic-action %d
	invalid users = root
	printing = cups
	print command = 
	lpq command = %p
	lprm command = 

[homes]
	comment = Home Directories
	path = /home/%S/
	valid users = %S
	read only = No
	create mask = 0751
	directory mask = 0751
	browseable = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	create mask = 0700
	printable = Yes
	browseable = No

[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers
	write list = root, @lpadmin

On Tue, Aug 21, 2007 at 05:25:21PM +0200, Thomas Flaig
wrote:
> I would like to have some samba-shares on a nfs-filesystem.
This is not supported. You should install Samba on the NFS
server, and possibly redirect your users using MS-DFS.

One potential workaround (no guarantees!) is to say "posix
locking = no" on the relevant shares.

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20070821/f50bc01d/attachment.bin

Hello,
Am Dienstag, 21. August 2007 17:57 schrieb Volker
Lendecke:
> On Tue, Aug 21, 2007 at 05:25:21PM +0200, Thomas Flaig wrote:
> > I would like to have some samba-shares on a nfs-filesystem.
> This is not supported.
Is this documented? Or better: Where is this documented?
I have not found hints to this limitation on the samba-webpage.
(I even did not find this limitation by searching for "inurl:samba.org 
nfs" on googel or just ignored that result).
> You should install Samba on the NFS 
> server, and possibly redirect your users using MS-DFS.
For the moment that would be a solution. Acctualy nfs is running on an 
rather old (and slow) linux server, there I could install (and configure) 
samba.

But this server was only reactivated because of some problems with our 
NAS.
The NAS crashed several times when we used samba and nfs (nfs3) at the 
same time. Acctually we do not knowwhy it crashed, but it seems safer to 
use only nfs (x)or smb.
> One potential workaround (no guarantees!) is to say "posix
> locking = no" on the relevant shares.
Here this did not solve the problem (neither with nfs3 nor with nfs4). :(
But on the web there are many reports where this was the solution.

Thomas
-- 
Thomas Flaig
mailto: thomas.flaig@unibw.de

On Wednesday 22 August 2007 11:43:47 Thomas Flaig wrote:
> > One potential workaround (no guarantees!) is to say "posix
> > locking = no" on the relevant shares.
>
> Here this did not solve the problem (neither with nfs3 nor with nfs4). :(
> But on the web there are many reports where this was the solution.

Can you try "locking = no"?


Cheers,
Bernd

-- 
Bernd Schubert
Q-Leap Networks GmbH

Am Mittwoch, 22. August 2007 12:36 schrieb Bernd
Schubert:
> On Wednesday 22 August 2007 11:43:47 Thomas Flaig wrote:
> > > One potential workaround (no guarantees!) is to say "posix
> > > locking = no" on the relevant shares.
> > Here this did not solve the problem (neither with nfs3 nor with
> > nfs4). :( But on the web there are many reports where this was the
> > solution.
> Can you try "locking = no"?
This did not solve our problem.

But Stefano Deponti suggested me today in a private mail:
| kernel oplocks = no
| to the global part of my smb.conf file.

With this option in the global-section and without the other options 
(locking = no; posix locking = no in the share-section) this 
configurations solves the problem.

Thomas
-- 
Thomas Flaig
mailto: thomas.flaig@unibw.de