similar to: Multiple instances of /usr/bin/smbd -D

Hello, We've been seeing a problem with Samba server 3.0.33-0.17 handling lock files for Microsoft Powerpoint 2007. The problem is observed in both Windows XP and Windows Vista. If a user opens an existing file, smbstatus looks like this: 10781 11021 DENY_WRITE 0x2019f RDWR NONE /usr/test/dssg test1234ecg2.pptx Fri Oct 23 17:21:52 2009 10517 11021

Hi I have problems with Samba and hope some of you can help me. Below if I have add the error messages that are relevant. [root at roskilde mosek]# emacs /var/log/samba/log.172.16.0.108 File Edit Options Buffers Tools Help [2014/02/06 10:18:29.562405, 0] smbd/oplock.c:330(oplock_timeout_handler) Oplock break failed for file windows/intel/Composer-XE-2013.198/Documentation/csupport.txt --

I noticed one of my smbd processes for one particular client (IUSR_JUNIPER) is taking 200MB in memory, far different from all the other smbd processes. Should I be concerned about a memory leak here? I don't think samba would be caching any files, so I can't see why it'd use this much memory. That windows client is a win2k IIS5 server, with well over 60 sites that are hosted off a

Dear all, I would need some help if we?re running in issues ?cause a wrong configuration of our shares, or it?s a bug in samba 4.12 On samba 4.11 we have no issues with our network shares when Windows Clients connect them. After upgrade to 4.12 we run in to the issue that network shares which are mounted as drives per gpo not working well, We get on windows when we try to open the network drive

Hi, We have 5 Samba domain controllers, and 4 file servers. All are 4.2.10-Debian. Our file servers have been working fine until recently (on the 26th), when suddenly access to the \\users.store.example.com\user share (hostname p-cats) became extremely slow. Access to other shares on other machines is fine, and users is 128G total (smaller than other shares). The machine isn't under

Hello I use a new samba server with LDAP support as PDC for some Windows2000 and WindowsXP machines. All is working nice. The useer can login with a user/password in the domain, we have remote profiles, the user can access the samba shares and print etc. But after some time (< 1 day) we get a smbstatus output like the attached file. Users are connected multiple times with the same share

Hello, I would like to how to do to kill the locked files from a useraccount by multiple smbd pids automatically when the session is closed? #### Details Samba server: Release: 5.10 Kernel architecture: sun4u Application architecture: sparc Hardware provider: Sun_Microsystems Kernel version: SunOS 5.10 Generic_142909-17 Samba version: Samba version 3.5.6 Smb.conf file section Global: #

I help an NT admin that has recently added a redhat 8.0 based samba server to his network. the share is one that is a core service for the operation of the business and has about 50 users constantly accessing data from several accounting and tax preparation applications. One of the primary applications requires update farily recently as of late and the admin is having problems getting all files

Hello everyone I moved my samba (3.6.9-168.el6_5) setup to new hardware and since the move a user can not write to the shared folders. When the file is opened by the user "smbstatus" shows: Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time

We have a central samba file share for our designers (who all use OSX boxes, and mostly use Macromedia products) to work off of. I've lately been able to track down a lot of application quirks (mostly problems with errors when saving, about files being locked) to the Mac resource fork files being indefinitely locked. Here's a sample from a `smbstatus` 14853 DENY_NONE 0x1

Hi Volker and the list Yesterday the problem appeared again I could launch a strace command over a samba PID to see what was going on and this is the result [PRO] [root at pf3il0024 ~]# strace -frp 57686 Process 57686 attached - interrupt to quit 0.000000 fcntl(14, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=35824, len=1} It seems the process was trying to get a read-lock but no one

I recently (a few weeks ago) installed 1.9.18p8 in order to get better performance with an Access Database, which along with adding a TCP_NODELAY in the [global] section has that working like a charm. Thing that's bugging me now is smbstatus. When I run it I see open files listed when I know that they aren't. The following output shows quite a few files open that aren't really. The

Hi Folks, Small office setup, 3 computers, 3 staff. Recently updated system and rebooted. Today, I am seeing crazy amounts of the same listing for clients (294 lines!) and open files... (snipped content below, you really don't want PAGES of it!) $ smbstatus Samba version 4.3.11-Ubuntu PID Username Group Machine Protocol Version

I am running samba 4.5.1 on Ubuntu 16.04. The samba server is running as an AD DC and stores the user profiles, the clients are all windows 10 professional. One user reported being locked out of the profile pretty regularly. After investigating the case I saw that a lot of files in the profile are still locked even after logging out and shutting down the system. After restarting the samba server,

I have 10 Windows 10 clients connecting to Ubuntu 16.04 with Samba version 4.3.11-Ubuntu. Each client has one smbd process, but I notice the number of child processes is exploding into 40.000+ the next day after a restart. I reckon this is not normal. Server load is < 0.1 but client applications are misbehaving and crashing. The problems started when moving from an old Ubuntu 10.04 to a newer

Have any of you seen behavior like this before? We are currently having problems with our Samba server coming up telling a lot of our users that Word files "are locked for editing." and will only let users open them Read Only. We are running Samba 2.2.5 from standard RedHat 7.2 RPMS, on i386 RedHat 7.2, Kernel 2.4.9-34smp. Im putting this to the list as a symptom to see if anyone has

Hi, I updated from Samba 2.2.5 to 2.2.8a. und Redhat 6.2 and since then, smbstatus shows strange values The dates and the pid's are wrong. Any ideas? Was there a change in a locking.tdb? Do I have to remove it? Greetings Hansj?rg 28643 DENY_NONE 0x3f407996 RDONLY LEVEL_II ?7??W? Tue Jan 6 22:38:12 1970 1633824626 0x706d622e NONE ?7??W? Thu Jan 1 02:00:00 1970 1836017711 0x56414143

On Fri, 25 May 2018 12:13:44 -0400 Raymond Page via samba <samba at lists.samba.org> wrote: > Hi list, > > I'm using samba-4.7.6-r0 and attempting to establish a public samba > share where any anonymous user can write to the share. > > I have an issue where the 'guest' (uid 405) account is unable to > write to a directory owned by that uid. If the gid or

hello, can anybody explain or point me to a document that explain the locked files section produced by smbstatus -L (see below). what means denymode ? access ? what means exclusive+batch in the oplock section ? can anybody point me to a document explaining the way file locking works ? regards # smbstatus -L Locked files: Pid DenyMode Access R/W Oplock Name

After having migrated my machines and user to Samba 4.3.11 on Ubuntu 16.04.1 (no domain upgrade, new provision, all accounts new defined) and old data copied over to the new machines, I have now a broader testbed and notice issues I didn't see prior to that. Having roaming profiles (defined in the user object in LDB)... Seemingly at random smbd keeps locks on NTUSER.DAT and ntuser.ini for a