Hi, I just joined this list and was searching the archives. I came across a thread "smbmounts hang around after windows client disconnects". Subject of thread was changed to "smbfs: process freezes on file copy". From December 4/5 2001. I am very interested in this old thread because I am having the EXACT same problem described. Certain files on my smbfs mount will freeze the copy process. Only a kill -9 will get my shell prompt back. I have a lot of information regarding the problem... -It only occurs with certain files. Roughly 1 out of every 50 or 100. I can't find anything in common with the problem files though. -Each file stops at the same respective spot EVERY time. -It has happened to me with a fairly default Red Hat 7.2 AND the latest Debian "woody". Debian is version 2.2.2debian-2. Red Hat was 2.2-something also. -The problem does NOT happen with a Red Hat 6.2 system! That machine has Samba 2.0.7 and 2.2.14-5 kernel. The Red Hat 7.2 system had kernel 2.4.7 I think. The Debian system has kernel 2.4.17. The files copy very nice and fast up until the point that they stop. I have tcpdumps. I will glady post portions to the list or via private email. Would very much appreciate any help! Thank you, Carl
Update on this: I wondered if the problem could be in my binary packages, so I installed Samba 2.2.2 from source on my Debian machine (2.4.17 kernel). No change. The same files freeze in the same spots. The only thing left that I can think to try is to boot a 2.2 kernel - going to try that next. Any other ideas??? Thanks, Carl> Certain files on my smbfs mount will freeze the copy > process. Only a kill -9 will get my shell prompt back. > > I have a lot of information regarding the problem... > > -It only occurs with certain files. Roughly 1 out > of every 50 or 100. I can't find anything in common > with the problem files though. > > -Each file stops at the same respective spot EVERY time. > > -It has happened to me with a fairly default Red Hat > 7.2 AND the latest Debian "woody". Debian is version > 2.2.2debian-2. Red Hat was 2.2-something also. > > -The problem does NOT happen with a Red Hat 6.2 system! > That machine has Samba 2.0.7 and 2.2.14-5 kernel. > > The Red Hat 7.2 system had kernel 2.4.7 I think. The > Debian system has kernel 2.4.17. > > The files copy very nice and fast up until the point > that they stop. > > I have tcpdumps. I will glady post portions to the list > or via private email.
HELP! My samba server keeps locking out my terminal server with permission denied errors.... This shows up in the samba logs... [2002/01/25 14:01:40, 1] smbd/password.c:add_session_user(338) Too many session users?? [2002/01/25 14:01:41, 1] smbd/session.c:session_claim(88) session_claim: out of session IDs (max is 3000) [2002/01/25 14:01:41, 1] smbd/password.c:register_vuid(316) Failed to claim session for vuid=4099 [2002/01/25 14:01:41, 1] smbd/password.c:add_session_user(338) Too many session users?? [2002/01/25 14:01:42, 1] smbd/session.c:session_claim(88) session_claim: out of session IDs (max is 3000) [2002/01/25 14:01:42, 1] smbd/password.c:register_vuid(316) Failed to claim session for vuid=4100
On Mon, 28 Jan 2002, Johnson, Carl wrote:> Hi, > > I just joined this list and was searching the archives. > > I came across a thread "smbmounts hang around after windows > client disconnects". Subject of thread was changed to > "smbfs: process freezes on file copy". From December > 4/5 2001.I'm not sure if I remember correctly, but that could have been something related to what he was doing with netware ... I don't think I ever got a trace on that.> I have tcpdumps. I will glady post portions to the list > or via private email.If you have full packet captures, please send them to me off-list unless they are huge (a few MBs are fine). Hopefully I can see what it is sending when it blocks. Do you also get that there is still traffic after it blocks? If all you have are stdout output from tcpdump then I don't think that will help me. It's very nice that it is so repeatable. /Urban
Anyone out there have any ideas for a fix for this? Please!!!!!!!!!! It is making the samba look bad to my management! Michael Joyner wrote:> HELP! > > My samba server keeps locking out my terminal server > with permission denied errors.... > > This shows up in the samba logs... > > [2002/01/25 14:01:40, 1] smbd/password.c:add_session_user(338) > Too many session users?? > [2002/01/25 14:01:41, 1] smbd/session.c:session_claim(88) > session_claim: out of session IDs (max is 3000) > [2002/01/25 14:01:41, 1] smbd/password.c:register_vuid(316) > Failed to claim session for vuid=4099 > [2002/01/25 14:01:41, 1] smbd/password.c:add_session_user(338) > Too many session users?? > [2002/01/25 14:01:42, 1] smbd/session.c:session_claim(88) > session_claim: out of session IDs (max is 3000) > [2002/01/25 14:01:42, 1] smbd/password.c:register_vuid(316) > Failed to claim session for vuid=4100 > > >
Another update on this problem. I tried a 2.2.20 kernel with smbfs support compiled in. Problem still there. The linux machine has two NICs, one a 3com and one an Intel, so I tried swapping those and having the other NIC handle the Samba traffic. Problem still there. I have exhausted all possibilities. I am really starting to wonder if it is some sort of hardware incompatibility, perhaps with my motherboard and/or IDE controller? The motherboard is a Supermicro P6SBA with a Pentium 733 MHz CPU. I'll keep plugging away but I'm pretty stumped now. There's no error messages or anything coming from smbfs or the kernel. The tcpdumps aren't very informative... traffic just seems to stop as far as I can tell. Carl
Last update - finally the problem is fixed! A rather interesting and perplexing solution... My Win2k machine uses a D-Link USB wireless ethernet device. It's what the file copies were using throughout this whole problem. I added a regular NIC to the Win2k machine and ran a long cable to the Linux Samba client and tried copying the same file - it worked! What's REALLY weird is now the wireless works fine too! I have no idea how, but adding the regular copper NIC fixed my problems. Maybe disabling/re-enabling the wireless adapter did it, maybe adding the new card did it, maybe the stars just aligned right... who knows... this is Windows we're talking about, after all. What I still don't understand is why other Samba clients could always copy okay from the same Win2k machine over wireless. Carl