Share is unable to be mounted because samba panics, thinking the drive is full.
I cleaned the logs, restarted samba and tried to log in from computer "miggyb"
[2007/07/18 06:25:02, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 11 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c293]
#1 /usr/sbin/smbd(smb_panic+0x46) [0x822c386]
#2 /usr/sbin/smbd [0x81dd58e]
#3 /usr/sbin/smbd(talloc_free+0xcb) [0x82326db]
#4 /usr/sbin/smbd(open_directory+0x343) [0x80d6ae3]
#5 /usr/sbin/smbd(reply_ntcreate_and_X+0xead) [0x80ae58d]
#6 /usr/sbin/smbd [0x80ea5b4]
#7 /usr/sbin/smbd(smbd_process+0x6f8) [0x80eb778]
#8 /usr/sbin/smbd(main+0x10df) [0x82c372f]
#9 /lib/libc.so.6(__libc_start_main+0x9e) [0x402d43be]
#10 /usr/sbin/smbd [0x8082b11]
[2007/07/18 06:25:02, 0] lib/fault.c:dump_core(168)
unable to change to /var/log/samba/cores/smbdrefusing to dump core
[2007/07/18 06:25:33, 1] smbd/service.c:make_connection_snum(950)
miggyb (192.168.1.89) connect to service stuff initially as user rodrigo (uid=1005, gid=100) (pid 1629)
[2007/07/18 06:25:33, 0] tdb/tdbutil.c:tdb_log(783)
tdb(/var/run/samba/locking.tdb): expand_file write of 1024 failed (No space left on device)
[2007/07/18 06:25:33, 0] lib/util.c:smb_panic(1599)
PANIC (pid 1629): Could not store share mode entry
my smb.conf is:
workgroup = WORKGROUP
netbios name = xboxy
security = share
guest account = rodrigo
force group = users
force user = rodrigo
guest only = yes
public = yes
writeable = yes
path = /Stuff
As you can see, user quotas are not implemented.
Running on debian, installed samba with apt-get. "path = /Stuff" is correct, the folder is really called "Stuff" and not "stuff". Client computer is a mac, running the latest os x update.
UPDATE: Turns out the hard drive really _was_ (for all practical purposes) full. It should still be able to be mounted as read-only, though, shouldn't it?
I deleted some things and now i'm able to connect from the client computer.
The problem here is the drive containing the tdb was full. We use that to store the open file records, so we can't function in this case. There's nothing we can do to fix this. We work if a drive is full, but not if the Samba database drive is full.