[Since samba-bugs has been shutdown, I'm posting this here...] I'm running RH 7.0 with both 2.2.16 and 2.4.2 kernels I've got the following samba packages installed: samba-client-2.0.7-21ssl samba-common-2.0.7-21ssl I have a Windows NT 4 server (SP6a) which stores many of my files since I use both Linux and Windows to access them (Linux on my desktop, Windows on my laptop) I don't access the shares at the same time (my desktop is usuall yoff when I use my laptop and vice versa) I mount 2 shares off my NT box: smbmount //baptiste_srv/mike ~/ntsrv -o username=xxxx,uid=yyyyyyy,password=uuuuuuuu,rw smbmount //baptiste_srv/NT_Junk ~/mp3 -o username=xxxx,uid=yyyyyyy,password=uuuuuuuu,rw I've done this as both root and the user yyyyyyy Obviously, the mp3 share is just that - nothing but mp3's. The first share stores common email and document files. I've found since I first put this system together that if I have 2 applications accessing SMB shares (not necessarily the same one) at the same time, the samba subsystem locks up along with the applications. It first happened at random it seemed when I had Netscape or Mozilla open (accessing my local mail files on the ntsrv share) and something else with an open document like Gnumeric or AbiWord. It would lock the apps up. Killing the parent process would leave defunt zombies that could NOT be killed. Even root kill -9 would not work. The problem became more obvious when I started playing MP3s in the background with XMMS. If I used my mail client or even opened/saved a file with gnumeric, it would SOMETIMES lock up. Note it is not immediate. However, playing MP3s increases the frequency of the problem. Note I use IMAP so I access my 'Local' email folders infrequently. It appears to be some type of problem when 2 applications issue SMB calls at the same time. Once it freezes, the shares are dead. Any application tryin gto access them (even 'df') will freeze when it gets to the SMB shares. The shares cannot be unmounted. Durin gshutdown, I get errors from smb_request as the system tries to unmount the shares. I get smb_request error=-512 setting invalid and then a few error=-3. It should be noted that sometimes during a shutdown when the shares are NOT forzen, I'll get error=-104 I believe though the shares to that point were functioning fine. When I've had just ONE applciation using a share - never had a problem. I've played MP3s for days straight - no problem. But open another app accessing different files or even a different share and it doesn't take long for hte shares to lock. I know this is light on debug info - is there any tool or /proc file that might shed some light on this? I can reproduce it fairly easily (just play MP3s and then do normal stuff :) ) Anyone seen behavior like this? Mike Baptiste mike@baptistefamily.net
Mike.. you might try posting this problem on guinness-list@redhat.com too. Gary Mike Baptiste wrote:> [Since samba-bugs has been shutdown, I'm posting this here...] > > I'm running RH 7.0 with both 2.2.16 and 2.4.2 kernels > I've got the following samba packages installed: > > samba-client-2.0.7-21ssl > samba-common-2.0.7-21ssl > > I have a Windows NT 4 server (SP6a) which stores many of my files since I > use both Linux and Windows to access them (Linux on my desktop, Windows on > my laptop) I don't access the shares at the same time (my desktop is usuall > yoff when I use my laptop and vice versa) > > I mount 2 shares off my NT box: > > smbmount //baptiste_srv/mike ~/ntsrv -o > username=xxxx,uid=yyyyyyy,password=uuuuuuuu,rw > smbmount //baptiste_srv/NT_Junk ~/mp3 -o > username=xxxx,uid=yyyyyyy,password=uuuuuuuu,rw > > I've done this as both root and the user yyyyyyy > > Obviously, the mp3 share is just that - nothing but mp3's. The first share > stores common email and document files. > > I've found since I first put this system together that if I have 2 > applications accessing SMB shares (not necessarily the same one) at the same > time, the samba subsystem locks up along with the applications. It first > happened at random it seemed when I had Netscape or Mozilla open (accessing > my local mail files on the ntsrv share) and something else with an open > document like Gnumeric or AbiWord. It would lock the apps up. Killing the > parent process would leave defunt zombies that could NOT be killed. Even > root kill -9 would not work. > > The problem became more obvious when I started playing MP3s in the > background with XMMS. If I used my mail client or even opened/saved a file > with gnumeric, it would SOMETIMES lock up. Note it is not immediate. > However, playing MP3s increases the frequency of the problem. Note I use > IMAP so I access my 'Local' email folders infrequently. It appears to be > some type of problem when 2 applications issue SMB calls at the same time. > > Once it freezes, the shares are dead. Any application tryin gto access them > (even 'df') will freeze when it gets to the SMB shares. > > The shares cannot be unmounted. Durin gshutdown, I get errors from > smb_request as the system tries to unmount the shares. I get smb_request > error=-512 setting invalid and then a few error=-3. > > It should be noted that sometimes during a shutdown when the shares are NOT > forzen, I'll get error=-104 I believe though the shares to that point were > functioning fine. > > When I've had just ONE applciation using a share - never had a problem. > I've played MP3s for days straight - no problem. But open another app > accessing different files or even a different share and it doesn't take long > for hte shares to lock. > > I know this is light on debug info - is there any tool or /proc file that > might shed some light on this? I can reproduce it fairly easily (just play > MP3s and then do normal stuff :) ) > > Anyone seen behavior like this? > > Mike Baptiste > mike@baptistefamily.net > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
On Wed, 28 Feb 2001, Mike Baptiste wrote:> I've found since I first put this system together that if I have 2 > applications accessing SMB shares (not necessarily the same one) at the same > time, the samba subsystem locks up along with the applications. It firstThe smbfs subsystem. The reason the apps lock up is that they are waiting for smbfs to respond.> document like Gnumeric or AbiWord. It would lock the apps up. Killing the > parent process would leave defunt zombies that could NOT be killed. Even > root kill -9 would not work.A defunct process is already dead, you can't kill it. It is waiting for the parent to collect them (but if the parent really is dead init should do that ...)> Once it freezes, the shares are dead. Any application tryin gto access them > (even 'df') will freeze when it gets to the SMB shares.One way to get this effect of complete lockup is if the server isn't responding (down). Which doesn't seem likely here.> The shares cannot be unmounted. Durin gshutdown, I get errors from > smb_request as the system tries to unmount the shares. I get smb_request > error=-512 setting invalid and then a few error=-3.-512 errors happens if the current process has caught a SIGSTOP or SIGKILL signal when smbfs tries to send something. It is a bug that usually causes the mount to stop working. You are sure you do not see these before unmounting? And you don't get any other messages from 'dmesg'? (Getting them at shutdown is expected).> It should be noted that sometimes during a shutdown when the shares are NOT > forzen, I'll get error=-104 I believe though the shares to that point were > functioning fine.You get these when the server disconnected and smbfs re-connected. They are not really errors (or rather, they are temporary errors).> When I've had just ONE applciation using a share - never had a problem. > I've played MP3s for days straight - no problem. But open another app > accessing different files or even a different share and it doesn't take long > for hte shares to lock.Can't say that I have ever seen this. Trying this now and it's doing just fine. Could you perhaps give a more detailed "script" of what you need to do to get a lockup? Something like: 1. start xmms (version?), 'xmms *.mp3 &' 2. start gnumeric on the same share and the same shell 3. edit the sheet 4. save in xyz format 5. repeat 3-4 for 10 minutes ...> I know this is light on debug info - is there any tool or /proc file that > might shed some light on this? I can reproduce it fairly easily (just play > MP3s and then do normal stuff :) )When the shares lock you could check what the processes are doing. 'ps -ln -p <pid>' for all pid's accessing smbfs. You could also, if you have enabled "sysrq debugging" press sysrq-t (alt gr - sysrq/print screen - t). This dumps all processes and the kernel call trace. Both of these are useless without a way to map the numbers to symbols. For that I'd need your System.map. If you have smbfs as a module, then I think I need the output of 'cat /proc/ksyms' too and the smbfs.o from /lib/modules/2.4.2/kernel/fs/smbfs/smbfs.o. Also a list of which processes are accesing which share. /Urban