[Samba] /var/lock/samba filling up /run/lock

[Mark Fox]

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 <achim at ag-web.biz> 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
>>
>
>