Apologies if this issue has been thrashed out already, but I'm having problems with using smbmount on samba 2.0.6 on Red Hat Linux 6.2 with the shares being dropped randomly. This can happen minutes or many hours after the share is mounted. I've heard of this problem before and the usual solution offered is to remount the shares. However, when I try to smbmount the share it says it is already mounted, and when I try an smbumount I get an input/output error and can't umount it. The only solution is to reboot the Linux box (logging out doesn't help). To mount the shares, I'm using .bash_profile entries as follows: /usr/bin/smbmount //NTSERVER/sharename /home/matt/sharename -o username=matt,password=pwd,uid=matt,gid=users,fmask=777,dmask=777,ip=192.168.0.2 This is so that each user gets their own mounts when they log in. I've also tried it with fstab with the same disconnection problem, but switched to .bash_profile so that remounts don't require a reboot (in theory, at least!). I had a look at the release notes for 2.0.7 and it didn't mention any fixes for this problem, so I've stuck with 2.0.6 for now. Does anyone know how to stop the disconnections from occurring? If not, any suggestions on how I can remount the shares without rebooting? Thanks! Matt _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Matt Doyle wrote:> > Apologies if this issue has been thrashed out already, but I'm having > problems with using smbmount on samba 2.0.6 on Red Hat Linux 6.2 with the > shares being dropped randomly. This can happen minutes or many hours after > the share is mounted. > > I've heard of this problem before and the usual solution offered is to > remount the shares. However, when I try to smbmount the share it says it is > already mounted, and when I try an smbumount I get an input/output error and > can't umount it. The only solution is to reboot the Linux box (logging out > doesn't help). >Matt, I have similar problems with shares mounted on a Win95 box. When you do smbmount, then umount, are you *sure* it didn't actually work? What I've seen is that one or both give you the error, but actually succeed in unmounting the disk.
On Fri, 8 Sep 2000, Matt Doyle wrote:> I've heard of this problem before and the usual solution offered is to > remount the shares. However, when I try to smbmount the share it says it isIt's not a solution, it's a workaround ...> already mounted, and when I try an smbumount I get an input/output error and > can't umount it. The only solution is to reboot the Linux box (logging out > doesn't help).The input/output error should have a matching kernel log message. Could you send it/them? Any difference between doing smbumount and plain umount?> To mount the shares, I'm using .bash_profile entries as follows: > > /usr/bin/smbmount //NTSERVER/sharename /home/matt/sharename -o > username=matt,password=pwd,uid=matt,gid=users,fmask=777,dmask=777,ip=192.168.0.2You may want to consider making smbmnt & smbumount setuid so anyone can mount using them, or switching to autofs (allows you to put the passwords in a root readonly file). The way you mount is not the problem.> I had a look at the release notes for 2.0.7 and it didn't mention any fixes > for this problem, so I've stuck with 2.0.6 for now.A problem that 2.0.7 also has is that smbmount may terminate if the server is rebooted. Also smbfs in most versions have problems with a process getting a signal while accessing smbfs. You can try 2.2.18pre3 that has a fix for the signal problem (but I broke a Config.in in 2.2.18pre3, so you need to change from a n to "n" if you use make xconfig) or 2.4.0-test7. I don't remember if the signal problem caused I/O errors on smbumount, but it could. If the server is rebooted (should be easy to check) you need to patch smbmount, http://www.hojdpunkten.ac.se/054/samba/index.html (You can choose between "dies-if-dies", "fixes" or "ascii+fixes" ... :) /Urban
>From: Urban Widmark <urban@svenskatest.se> > > > I've heard of this problem before and the usual solution offered is to > > remount the shares. However, when I try to smbmount the share it says >it is > >It's not a solution, it's a workaround ...Sorry, I meant to say workaround!> > already mounted, and when I try an smbumount I get an input/output error >and > > can't umount it. The only solution is to reboot the Linux box (logging >out > > doesn't help). > >The input/output error should have a matching kernel log message. Could >you send it/them? Any difference between doing smbumount and plain umount?I'm not that familiar with Linux I must admit, but I assume the messages you're after are in /var/log/messages? The corresponding message for the input/output error is: "smb_retry: signal failed, error=-3" I also found these other messages in the log: "smb_trans2_request: result=-32, setting invalid" Not sure when these are being generated though. I actually found that doing a plain umount works fine! Thanks for that - I no longer have to reboot each time. :) It's just the smbumount that fails with the input/output error and corresponding "signal failed" message.> > To mount the shares, I'm using .bash_profile entries as follows: > > > > /usr/bin/smbmount //NTSERVER/sharename /home/matt/sharename -o > > >username=matt,password=pwd,uid=matt,gid=users,fmask=777,dmask=777,ip=192.168.0.2 > >You may want to consider making smbmnt & smbumount setuid so anyone can >mount using them, or switching to autofs (allows you to put the passwords >in a root readonly file).I'd actually already setuid smbmount - should I be setuid'ing smbmnt instead?> > I had a look at the release notes for 2.0.7 and it didn't mention any >fixes > > for this problem, so I've stuck with 2.0.6 for now. > >A problem that 2.0.7 also has is that smbmount may terminate if the server >is rebooted. Also smbfs in most versions have problems with a process >getting a signal while accessing smbfs.So is this probably the reason for the disconnections?>You can try 2.2.18pre3 that has a fix for the signal problem (but I broke >a Config.in in 2.2.18pre3, so you need to change from a n to "n" if you >use make xconfig) or 2.4.0-test7. I don't remember if the signal problem >caused I/O errors on smbumount, but it could. > >If the server is rebooted (should be easy to check) you need to patch >smbmount, http://www.hojdpunkten.ac.se/054/samba/index.html >(You can choose between "dies-if-dies", "fixes" or "ascii+fixes" ... :)OK - I'll check that out. Thanks! Best wishes, Matt.> >/Urban > >_________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
I found some more smb_* messages in the log: Sep 7 17:15:17 muddy kernel: smb_trans2_request: result=-32, setting invalid Sep 7 17:15:17 muddy kernel: smb_retry: new pid=877, generation=6 Sep 7 17:15:18 muddy kernel: smb_trans2_request: result=-32, setting invalid Sep 7 17:15:18 muddy kernel: smb_retry: new pid=874, generation=6 Sep 7 17:15:18 muddy kernel: smb_trans2_request: result=-32, setting invalid Sep 7 17:15:19 muddy kernel: smb_retry: new pid=1130, generation=3 Sep 7 18:06:08 muddy kernel: smb_trans2_request: result=-32, setting invalid Sep 7 18:06:08 muddy kernel: smb_retry: caught signal Sep 7 18:06:08 muddy last message repeated 3 times Sep 7 18:06:08 muddy kernel: smb_lookup: find members_bens/salesquestionnaire_sendmail.asp failed, error=-5 Sep 7 18:06:08 muddy kernel: smb_retry: caught signal Sep 7 18:06:08 muddy last message repeated 3 times Sep 7 18:06:08 muddy kernel: smb_lookup: find members_bens/salesquestionnaire_sendmail.asp failed, error=-5 Sep 7 18:06:08 muddy kernel: smb_retry: caught signal Sep 7 18:06:08 muddy last message repeated 3 times Sep 7 18:06:08 muddy kernel: smb_lookup: find members_bens/salesquestionnaire_sendmail.asp failed, error=-5 Sep 7 18:06:08 muddy kernel: smb_retry: caught signal Sep 7 18:07:35 muddy kernel: smb_retry: signal failed, error=-3 Sep 7 18:07:35 muddy last message repeated 3 times Hope that helps! Matt>From: Urban Widmark <urban@svenskatest.se> >To: Matt Doyle <matt_the_bishop@hotmail.com> >CC: samba@us4.samba.org >Subject: Re: smbmount on NT4 shares disconnecting randomly >Date: Sun, 10 Sep 2000 21:17:00 +0200 (CEST) > >On Sun, 10 Sep 2000, Matt Doyle wrote: > > > I'm not that familiar with Linux I must admit, but I assume the messages > > you're after are in /var/log/messages? The corresponding message for >the > > input/output error is: > > > > "smb_retry: signal failed, error=-3" > > > > I also found these other messages in the log: > > > > "smb_trans2_request: result=-32, setting invalid" > >Yes, that is what I was looking for ... sort of. No other smb_* messages ? > > > I actually found that doing a plain umount works fine! Thanks for that >- I > > no longer have to reboot each time. :) It's just the smbumount that >fails > > with the input/output error and corresponding "signal failed" message. > >smbumount does some tests before unmounting, I think one of those accesses >the mountpoint which fails with an EIO. > > > > I'd actually already setuid smbmount - should I be setuid'ing smbmnt > > instead? > >That is how I understand it, see the manpage for smbmnt. > > > > >A problem that 2.0.7 also has is that smbmount may terminate if the >server > > >is rebooted. Also smbfs in most versions have problems with a process > > >getting a signal while accessing smbfs. > > > > > > So is this probably the reason for the disconnections? > >It's probably not uncommon, but you should get a "caught signal" message. >If you don't get a "caught signal" then that is not your problem. > >/Urban > >_________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.