similar to: Samba Very Slow When Using AFS and MS Office (is this a Bug?)

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

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,

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

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

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]:

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

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

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

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 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

On 2014?03?08? 20:57, Gene Cumm wrote: > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > >> > Another thing you I'd like to mentioned is, after bootx64.efi was >> > downloaded, the next download for ldlinux.e64 was about 15 secs later. >> > Is that normal? > When it's successful for me, it takes 0.2s from the beginning of >

Hi, we have a strange samba locking problem with version 3.0. Sometimes user only get a read only access to files. This happens with different users on different clients. Unix permissions are OK. I have realy no idea. Can you help ? Thanx Peter Huber -------------- next part -------------- [2004/03/02 15:03:56, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0)

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:

Hi, I have tried to get my Win2K to access my Linux Samba server without success. The error message I am getting is "Network Path not found". Below are the details: 1. The Win2K is actually a guest OS running on VMWare-2.0.4. The host OS is a RedHat 7.2. VMware uses samba-2.0.6. 2. The config file was based on a working sample, off another VMWare machine. Its host OS was RedHat 7.2

Hello, i'm using a debian etch box (2.6.18-5-686) with tinc 1.0.5 for connecting to my office LAN. On the same box there's a vmware virtual machine running (Windows 2k). Now i'd like to connect this virtual machine through the VPN, too. All my attempts did fail... The virtual machine runs with a "host only" network (vmnet1). On the linux side i tried to configure NAT

Hi all, I've dug into a problem I've been having with Samba-3.0.0 (trying out 3.0.1 right now) on a linux system (2.4.18-3 kernel) with glibc 2.2.5 ... when I run a ./configure (with or without --with-spinlocks) it tests out my fcntl.h, and it fails the first fcntl.h test, the following one (where it tests for a broken glibc 2.1), but then passes the 64 bit fcntl test!? Now when it

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)