On Tue, Jan 27, 2009 at 08:50:11PM +0100, Daniel Polak wrote: > Just clicking on a mapped drive results in the following: > Jan 27 20:36:02 fileserver smbd[10133]: [2009/01/27 20:36:02, 0] > /usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:write_data(562) > Jan 27 20:36:02 fileserver smbd[10133]: write_data: write failure in > writing to client 192.168.1.102. Error Broken pipe > Jan 27 20:36:02 fileserver smbd[10133]: [2009/01/27 20:36:02, 0] > /usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util_sock.c:send_smb(761) > Jan 27 20:36:02 fileserver smbd[10133]: Error writing 4 bytes to > client. -1. (Broken pipe)
Ok, these are normal. > Running the database operation that is causing problems show this now: > Jan 27 20:39:26 fileserver smbd[31888]: [2009/01/27 20:39:26, 0] > /usr/obj/i386/samba-3.0.31/samba-3.0.31/source/lib/util.c:smb_panic(1633) > Jan 27 20:39:26 fileserver smbd[31888]: PANIC (pid 31888): Could not > store byte range mode entry This one is really, really strange. Can you run strace on the smbd that does this (with use mmap=no) ? Thanks, Volker
pgp5SgmKPLVDk.pgp
Description: PGP signature
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
