smbmount on NT4 shares disconnecting randomly

Matt Doyle matt_the_bishop at
Sun Sep 10 18:50:04 GMT 2000

>From: Urban Widmark <urban at>
> > 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 
> > can't umount it.  The only solution is to reboot the Linux box (logging 
> > 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
> > 
>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 

> > I had a look at the release notes for 2.0.7 and it didn't mention any 
> > 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 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
>(You can choose between "dies-if-dies", "fixes" or "ascii+fixes" ... :)

OK - I'll check that out.  Thanks!

Best wishes,


Get Your Private, Free E-mail from MSN Hotmail at

Share information about yourself, create your own public profile at

More information about the samba mailing list