samba - Jan 2009 - Microsoft Access MDB database on Samba share

I'm having problems using Microsoft Access 2000 mdb files on a Samba share.
The same database worked very well on a Windows server.

I had hoped Samba would be a drop in replacement for a Windows server 
but apparently Access needs special Samba configuration.

In Access I sometimes get Run-time error '3035': System resource
exceeded.
I don't see any errors in the log file when this is happening.

Concurrent access to the database doesn't work well either.

The log shows the following for yesterday: These messages maybe not be 
related to my Access database problem but they still worry me a bit:

Jan 26 10:14:32 fileserver smbd[3850]: [2009/01/26 10:14:32, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util.c:smb_panic(1633)
Jan 26 10:14:32 fileserver smbd[3850]:   PANIC (pid 3850): Could not 
store byte range mode entry
Jan 26 10:14:32 fileserver smbd[3850]:
Jan 26 10:14:32 fileserver smbd[3850]: [2009/01/26 10:14:32, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util.c:log_stack_trace(1787)
Jan 26 10:14:32 fileserver smbd[3850]:   unable to produce a stack trace 
on this platform
Jan 26 10:14:32 fileserver smbd[3850]: [2009/01/26 10:14:32, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/fault.c:dump_core(181)
Jan 26 10:14:32 fileserver smbd[3850]:   dumping core in /var/log/cores/smbd
Jan 26 10:14:32 fileserver smbd[3850]:
Jan 26 10:14:38 fileserver smbd[1771]: [2009/01/26 10:14:38, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:set_socket_options(261)
Jan 26 10:14:38 fileserver smbd[1771]:   Failed to set socket option 
TCP_NODELAY (Error Connection reset by peer)
Jan 26 10:14:38 fileserver smbd[1771]: [2009/01/26 10:14:38, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:get_peer_addr(1224)
Jan 26 10:14:38 fileserver smbd[1771]:   getpeername failed. Error was 
Socket is not connected
Jan 26 10:14:38 fileserver smbd[1771]: [2009/01/26 10:14:38, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:write_data(562)
Jan 26 10:14:38 fileserver smbd[1771]:   write_data: write failure in 
writing to client 192.168.8.82. Error Broken pipe
Jan 26 10:14:38 fileserver smbd[1771]: [2009/01/26 10:14:38, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:send_smb(761)
Jan 26 10:14:38 fileserver smbd[1771]:   Error writing 4 bytes to 
client. -1. (Broken pipe)
Jan 26 12:40:51 fileserver smbd[23103]: [2009/01/26 12:40:51, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:get_peer_addr(1224)
Jan 26 12:40:51 fileserver smbd[23103]:   getpeername failed. Error was 
Socket is not connected
Jan 26 12:40:51 fileserver smbd[23103]: [2009/01/26 12:40:51, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:write_data(562)
Jan 26 12:40:51 fileserver smbd[23103]:   write_data: write failure in 
writing to client 192.168.8.209. Error Broken pipe
Jan 26 12:40:51 fileserver smbd[23103]: [2009/01/26 12:40:51, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:send_smb(761)
Jan 26 12:40:51 fileserver smbd[23103]:   Error writing 4 bytes to 
client. -1. (Broken pipe)
Jan 26 14:06:19 fileserver smbd[10362]: [2009/01/26 14:06:19, 0] 
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/smbd/nttrans.c:call_nt_transact_ioctl(2463)
Jan 26 14:06:19 fileserver smbd[10362]:   
call_nt_transact_ioctl(0x9009c): Currently not implemented.


Samba version is 3.0.31 running on OpenBSD 4.4 current (from August last 
year).

smb.conf:
[shared]
   comment = file exchange
   path = /var/fileserver
   read only = no
   browseable = yes
   create mask = 0774
   force create mode 0774
   oplocks = False
   level2 oplocks = False


What is the recommended Samba configuration for use with Microsoft 
Access databases?
What is causing the error messages in the log?

Daniel

On Tue, Jan 27, 2009 at 05:04:19PM +0100, Daniel Polak
wrote:
> Jan 26 10:14:32 fileserver smbd[3850]: [2009/01/26 10:14:32, 0] 
> /usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util.c:smb_panic(1633)
> Jan 26 10:14:32 fileserver smbd[3850]:   PANIC (pid 3850): Could not 
> store byte range mode entry
full disk?

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20090127/7aa95891/attachment.bin

==== Original message from Volker Lendecke at 27-1-2009
17:58
> On Tue, Jan 27, 2009 at 05:04:19PM +0100, Daniel Polak wrote:
>   
>> Jan 26 10:14:32 fileserver smbd[3850]: [2009/01/26 10:14:32, 0] 
>>
/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util.c:smb_panic(1633)
>> Jan 26 10:14:32 fileserver smbd[3850]:   PANIC (pid 3850): Could not 
>> store byte range mode entry
>>     
>
> full disk?
Not really!
# df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/sd0e     39.4G    980M   36.4G     3%    /var

On Tue, Jan 27, 2009 at 07:45:24PM +0100, Daniel Polak
wrote:
> ==== Original message from Volker Lendecke at 27-1-2009 17:58
> >On Tue, Jan 27, 2009 at 05:04:19PM +0100, Daniel Polak wrote:
> >  
> >>Jan 26 10:14:32 fileserver smbd[3850]: [2009/01/26 10:14:32, 0] 
>
>>/usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util.c:smb_panic(1633)
> >>Jan 26 10:14:32 fileserver smbd[3850]:   PANIC (pid 3850): Could
not
> >>store byte range mode entry
> >>    
> >
> >full disk?
> Not really!
> # df -h
> Filesystem     Size    Used   Avail Capacity  Mounted on
> /dev/sd0e     39.4G    980M   36.4G     3%    /var
This is OpenBSD, right? It used to have a badly broken mmap
implementation. You might try "use mmap = no".

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20090127/908cb5b6/attachment.bin