Re: [Samba] /var/lock/samba filling up /run/lock
Hi Mark, On Mon, Aug 19, 2013 at 11:06:55AM -0600, Mark Fox wrote: > Thanks Achim, especially for pointing out where we can set the size of > /run/lock and have it stick after a reboot. We hadn't gotten that far yet, > but we did expand the size of /run/lock on Friday by hand and do some > testing. We ended up chasing an unrelated wild goose, but realized this > morning that simply expanding /run/lock does look like a viable workaround. > > Also, in exploring the problem, we're seeing about 300KB being chewed up in > /run/lock with every new user that logs in. To be clear, this only seems to > happen the first time a user logs in. I'm not sure if that is a symptom of > a problem, or just normal operation. We've also noticed that a version of > Samba 4 built from source taken from the Git repository puts its lock files > under /usr/local/samba, completely avoiding the problem. > > Since the Sernet packages use /run/lock, I imagine this will be a problem > for anyone with more than about a dozen users. They might want to point > Samba somewhere else to store its locks. we changed the directory for tdb files containing non-persistent data to /var/cache/samba/ to work around very limited tmpfs partitions in our SerNet packages. It should be fixed with Samba 4.0.9-5 RPMs and 4.0.9-6 debs. Maybe you would like to update. Thanks! Cheers, Karolin -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.SerNet.DE, mailto:kont...@sernet.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] /var/lock/samba filling up /run/lock
Thanks Achim, especially for pointing out where we can set the size of /run/lock and have it stick after a reboot. We hadn't gotten that far yet, but we did expand the size of /run/lock on Friday by hand and do some testing. We ended up chasing an unrelated wild goose, but realized this morning that simply expanding /run/lock does look like a viable workaround. Also, in exploring the problem, we're seeing about 300KB being chewed up in /run/lock with every new user that logs in. To be clear, this only seems to happen the first time a user logs in. I'm not sure if that is a symptom of a problem, or just normal operation. We've also noticed that a version of Samba 4 built from source taken from the Git repository puts its lock files under /usr/local/samba, completely avoiding the problem. Since the Sernet packages use /run/lock, I imagine this will be a problem for anyone with more than about a dozen users. They might want to point Samba somewhere else to store its locks. Mark A. Fox, M.Sc. Director of Technology East Central Alberta Catholic Schools Cell: 403-740-6101 Office: 780-842-3992 On Fri, Aug 16, 2013 at 6:28 PM, Achim Gottinger wrote: > Am 16.08.2013 17:49, schrieb Mark Fox: > > A couple of days ago, we noticed the following message appearing in >> syslog: >> >> Aug 14 15:09:35 zadok smbd[16067]: tdb(/var/lock/samba/locking.**tdb): >> expand_file write of 8192 bytes failed (No space left on device) >> >> Had this issue on my debian setup. /run/lock is a tmpfs volume. It's > size is defined in /etc/defaults/tmpfs on debian. I increased it from 5 to > 50Mib (LOCK_SIZE=52428800) and had no isses since. > > achim+ > > >> Mark >> > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] /var/lock/samba filling up /run/lock
Am 16.08.2013 17:49, schrieb Mark Fox: A couple of days ago, we noticed the following message appearing in syslog: Aug 14 15:09:35 zadok smbd[16067]: tdb(/var/lock/samba/locking.tdb): expand_file write of 8192 bytes failed (No space left on device) Had this issue on my debian setup. /run/lock is a tmpfs volume. It's size is defined in /etc/defaults/tmpfs on debian. I increased it from 5 to 50Mib (LOCK_SIZE=52428800) and had no isses since. achim+ Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] /var/lock/samba filling up /run/lock
A couple of days ago, we noticed the following message appearing in syslog: Aug 14 15:09:35 zadok smbd[16067]: tdb(/var/lock/samba/locking.tdb): expand_file write of 8192 bytes failed (No space left on device) Similar messages would show up for several of the files under /var/lock/samba. Running df showed that /run/lock was full. Not having ever paid any attention to /run/lock before, I thought that this was normal, but RiXtEr clued me in on #samba. There was a difference in the reported size of the lock files in /var/lock/samba depending on whether we used 'ls -l' or 'du -s'. Two files were about 4GB in size as reported by 'ls' and well under 5MB (the size of /run/lock) as reported by 'du'. The big files were locking.tdb and smbXsrv_open_global.tdb, Restarted Samba brought those files down to...very small. But we've noticed that they grow quite quickly, seemingly whenever a new user logs in (but we're really nt sure of that). Right now, /run/lock is sitting at 54% (2.7MB). This is just in a testing environment, with four workstations and twenty test users. Some of the production environments that we are aiming to roll out real soon would have more than 100 workstations and several hundred users. The Samba4 server is running Ubuntu 12.04LTS and the Sernet packages from the PPA. Our configuration is quite simple, just a Samba4 PDC/AD with a share for redirected user folders using the built-in LDAP and DNS. We will have two more test environments up and running shortly and could use them to test, compare, and contrast. Any suggestions for what to try are welcome. If we see that one of the test environments doesn't exhibit these symptoms, we'll try to home in on the difference. Should this be posted to samba-technical? Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
