similar to: configure incorrectly assumes my linux system is 64 bit capable

Hi all, I've got kind of strange setup, wherein all of my data is on a big NFS server (RH linux 8.0 running the 2.4.18 kernel and nfs-utils 1.0.1-2.80) and my Samba 3.0.0 PDC server (RH linux 7.3 w/ 2.4.18 kernel, nfs-utils 0.3.3-6.73) mounts the NFS export with the following options: rw,vers=3,wsize=8192,rsize=8192,hard,intr This mounted partition is then re-exported to the windows users

Hello list, I've got a problem concerning locking of files with a share on a nfs mounted NAS. samba server is 2.2.8a installed from SuSE-RPMs the NAS is mounted with following line in fstab: <IP-Number>:/vgroup00/data02/data /mnt/nas01 nfs rsize=8192,wsize=8192,soft 0 0 I tried to save a file from word which lead to a aprox. 1 minute hang of my Win2k/SP3. The log of the

Sorry if this issue has come up before. I have been using samba on a NetApp filer successfully for some time but I recently upgraded my samba server to Suse 9.0 Professional. I am trying to use the 'classic samba' version (since I don't know any better) and am having problems with file locking on my shares. Here is a transcript of the log.smbd that shows some incompatibility between

Well, next problem. Because of samba isn't running on alphaserver 1200 with gentoo linux and kernel 2.6.9-ac12 i've simply exported my smbroot (on alpha, it is my fileserver) and have samba running on an intel pentium4 box, also gentoo, kernel 2.6.0-ac12. Seems to work, eccept some locking problems. smbd[9450]: [2005/02/08 17:29:51, 0] locking/posix.c:posix_fcntl_lock(657) smbd[9450]:

Hi, Is there a known issue with FreeBSD 5.2.1 and Samba 3.0.4? I am getting file corruption when copying to a local FAT32 drive (mounted under FBSD) from a Windows XP Pro workstation. There doesn't seem to be any pattern in the corruption. If I mount an UFS drive, everthing is fine. I'd also like to find out if the corruption would also have affected file updates, and not just new file

I was trying to copy swf file (35MB) from a windows machine to my samba share. It told me "There is not enough disk space". However, it lets me copy it in another share. I didn't notice anything different with the share I am having problem with. I noticed the following messages in the log: [2005/08/10 13:56:47, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 2GB of transfer, files stop being written by Samba. I keep getting Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(656) Jun 12 11:29:37 nasserver smbd[8715]: posix_fcntl_lock: WARNING: lock request at offset 558761983, length 1 returned Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37,

I am using 3.0.13 and have temporarily run out of disk space on the main samba server, so I have NFS mounted some space from another machine. into a directory that is accessible under samba. When I try to save directly from ms word 2003 sp1 (and same from word 2000) it tells me: on the win98se and win xp pro sp2 clients: "Microsoft Office Word" Word cannot complete the save due to

I ran into this problem and was unable to find a solution here or in google. Thought I'd post it to the list so maybe it'll help someone out in the future. Gentoo Linux running 2.4.22 and Samba 2.2.8a. ReExporting an NFS mounted share on a NetAPP fileserver connected to eth1 via samba out eth0. All PCs are able to write fine but when writing to the share via a mac using OSX the

We are receiving the following in our logs: Mar 18 13:41:37 athena smbd[24222]: [2005/03/18 13:41:37, 0] locking/posix.c:posix_fcntl_lock(658) Mar 18 13:41:37 athena smbd[24222]: an Invalid argument error. This can happen when using 64 bit lock offsets Mar 18 13:41:37 athena smbd[24222]: [2005/03/18 13:41:37, 0] locking/posix.c:posix_fcntl_lock(659) Mar 18 13:41:37 athena smbd[24222]: on 32

When an XP box is reading a file from the Samba server performance is what you would expect with 100 mbs ethernet. When uploading a large file (>1 meg) performance is very slow. 1/20th what I would expect. The Samba server log has these entries: posix_fcntl_lock: WARNING: lock request at offset 12226560, length 61440 returned [2004/12/24 17:28:52, 0] locking/posix.c:posix_fcntl_lock(658)

Good day, Our Windows users aren't able to edit their MS Office files over our Samba shares (Samba 3.0.10, CentOS4 w/ their i386 RPM). It looks like the clients' attempts to lock the files fails. When their client attempts to open such a file, Samba reports: ----------8<----------------------- [2006/10/27 15:55:57, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock:

Hello -- I recently installed Samba 3.0.1 on our Solaris 8 servers (as well as our RedHat servers) and I wanted to see if I could get some feedback on a few things. We are using Samba in conjunction with Clearcase for our software developers and because of that, we have oplocks turned off (also level2 oplocks = no as well). We are authenticating to our ADS server, but joining the domain with

Hi all, I'm setting up a number of samba DC's across several branch offices using the Samba 3.0.0 release's native LDAP support. I'd like to build some redundancy into my setup, such as having slave LDAP servers in case the master is down/unavailable. However, when I have multiple ldapsam entries in my smb.conf I get duplicate or triplicate users listed when performing a

Hi all, I've tried searching all over the net for any information about this error but can't seem to find any. I've compiled Samba 2.2.8a on a RH Linux 7.3 box (kernel 2.4.18-3) with lsapsam support against openldap 2.0.23-4. I'm also using pam_ldap such that all authentication (unix + samba/windows) is done through LDAP, which is working quite nicely. However, none of my NT

On Nov. 5, Juergen Bock wrote (in a message titled "32/64bit locking problem with 2.2.2") that he was seeing a 32/64bit locking error in his logs. I have also seen this problem. I have a little more information that indicates that this behavior started after samba version 2.2.0a. Here are the samba versions I have tested: Samba 2.2.0a (compiled on rh7.1 system with kernel 2.4.5)

Hi All, I am having a problem with Samba that seems to be a bug. I say this because I read the archives and they described a problem similar to mine and were told that it was a bug in older version of Samba and the latest version should have it fixed. I am running what is essentially a RH 7.3 on a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5 and am using the following

There seems to be a few people having this problem, but not much response. I've dug into the logs, and while I don't know exactly what I am looking at, I think I may have found something that may make sense to someone. A short recap. Samba was working fine, until I did a Debian security update, which upgraded my Samba to 2.2.8a. Now, I can create files on a mounted Samba share in a

Hi Samba Team, I tried samba 2.2.8a (without winbind) on HPUX 11/32. I downloaded the binaries from http://de.samba.org/samba/ftp/Binary_Packages/hp/samba-2.2.8a/ I get following errors: [2003/06/27 10:16:50, 0] locking/posix.c:(658) an Invalid argument error. This can happen when using 64 bit lock offsets [2003/06/27 10:16:50, 0] locking/posix.c:(659) on 32 bit NFS mounted file systems.

Hi there, I have a quite ugly problem with a Samba server. The server is running Linux 2.4.13 and Samba 2.2.2. The NFS-client is running Linux 2.4.5. The windows homedirs are on \\server\username, the UNIX homedirs are NFS mounted by the server. So, whenever I access \\server\username this actually NFS-mounts /nfs/client/home/username. I now have one client machine that causes the following