(CC'ing to lkml in hope on advise why I've got ksymoops error)
Hello Urban,
My Samba server behaves strangely.
Very frequently (but not always) when I try to create/copy
files from win box to linux samba server it says that file/dir
already exists or that connection terminated. It is indeed exists,
in case of a file it is of zero length. Subsequent copy with
overwrite succeeds.
It seems that smbd dies after it has created dir/file but before
reporting this fact to the client. New smbd gets spawned by inetd
then.
It might be related to newer kernel.
I am willing to track it further.
Samba: 2.2.1a
Kernel: 2.4.10
Also I've got two oopses so far. One of them decoded below
(my first ksymoops, I don't know is it done right on not)
--------------------------------------------
ksymoops 2.4.3 on i686 2.4.10. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.10/ (default)
-m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information....
<snip>
Unable to handle kernel paging request at virtual address 4008e6ed
*pde = 01100067
Oops: 0003
CPU: 0
EIP: 0010:[<c010655b>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: 4008e76d ecx: 4008e6cd edx: 0000e865
esi: 00000000 edi: 00000128 ebp: 4008e6c9 esp: c1c5bf74
ds: 0018 es: 0018 ss: 0018
Process smbd (pid: 213, stackpage=c1c5b000)
Stack: 5650faf0 c1c5a000 c029afd0 00000128 c01068d0 4008e6cd 4008e76d c1c5bf94
c02a23b2 55c3c85e ec83e589 4000bcd9 40015f67 4000bcd9 40015f67 c1c5a000
00000000 00000000 bfffea74 c0107603 00000000 bfffe6a3 00000001 00000000
Call Trace: [<c01068d0>] [<c0107603>]
Code: 89 51 20 31 c0 66 8b 53 0c 81 e2 ff ff 00 00 09 c6 89 51 1c
Error (Oops_bfd_perror): set_section_contents Section has no contents
>>EIP; c010655a <restore_sigcontext+3a/140> <=====
Trace; c01068d0 <sys_rt_sigreturn+110/180>
Trace; c0107602 <system_call+32/40>
1 warning and 1 error issued. Results may not be reliable.
--
Best regards, vda
mailto:[email protected]
On Tue, 16 Oct 2001, vda wrote:
> My Samba server behaves strangely.
You are confusing me with someone that knows something about samba as a
server (or restore_sigcontext :)
> It seems that smbd dies after it has created dir/file but before
> reporting this fact to the client. New smbd gets spawned by inetd
> then.
If a syscall crashes I think you can't blame smbd for causing strange
effects for the client. I think you should "hunt" the kernel crash first,
if smbd still acts funny when the kernel doesn't crash ask for help on the
[email protected] maillist.
> Samba: 2.2.1a
> Kernel: 2.4.10
Try repeating the problem with 2.4.13-pre3 (or whatever the latest may be)
and if you can do that post another decoded oops of that, with a subject
containing the words "Oops" and "restore_sigcontext" (if that is still in
the decoded oops).
That will hopefully make your message reach the right audience. You may
also have a look at REPORTING-BUGS for hints on how to list your system
cfg.
Samba 2.2.2 is just out, but I don't think upgrading will help.
> Also I've got two oopses so far. One of them decoded below
> (my first ksymoops, I don't know is it done right on not)
Looks fine, not that it tells me much. It usually disassembles the part
where it crashes and that can be helpful to people that know the code
in question. Not sure why it didn't here, did you edit it out?
/Urban
On Tue, 16 Oct 2001, vda wrote:
> (CC'ing to lkml in hope on advise why I've got ksymoops error)
>
> Hello Urban,
>
> My Samba server behaves strangely.
> Very frequently (but not always) when I try to create/copy
> files from win box to linux samba server it says that file/dir
> already exists or that connection terminated. It is indeed exists,
> in case of a file it is of zero length. Subsequent copy with
> overwrite succeeds.
>
> It seems that smbd dies after it has created dir/file but before
> reporting this fact to the client. New smbd gets spawned by inetd
> then.
Following my fading memory here, but....
What file system are you sharing? VFAT by chance? For some reason
this sounds vaguely like a truncate bug Tridge fixed a few monthds
back. Try 2.2.2 (released over the weekend).
If you are exporting a VFAT fs, try to reproduce the same behavior
using ext2.
cheers, jerry
---------------------------------------------------------------------
http://www.samba.org SAMBA Team jerry_at_samba.org
http://www.plainjoe.org jerry_at_plainjoe.org
--"I never saved anything for the swim back." Ethan Hawk in Gattaca--