smbfs glitch

Charles Howes croot at
Sun Jan 21 01:49:01 GMT 2001

On Sat, 20 Jan 2001, Urban Widmark wrote:

> > It almost worked, except that I was forced to try and mount a share that
> > had a space in it.  There is no way to specify spaces in pathnames in
> > /etc/fstab, neither quotes nor backslashes had any effect.
> If mount won't allow spaces to be escaped with \ then maybe mount should
> be fixed?

It probably should.  At the time, I was up against a deadline; the
perl script was the fastest way to do it.

> > since the NT share *sometimes* goes weird.  Note, this only does
> > something when 'ls' returns an error.  If /ftp is completely
> > mounted or unmounted, there is no error.
> What kernel are you using? Do you get error messages from the kernel when
> this happens? Does 2.2.18 work any better for you?

The output is:

# ls /ftp
ls: /ftp: Input/output error
session setup failed: code 0
SMB connection failed
# umount /ftp
# mount /ftp
mount: backgrounding "//mini_me_1/FTP%20Share"

And the log says:
Nov 30 17:14:14 puma kernel: smb_trans2_request: result=-32, setting invalid 
Nov 30 17:14:19 puma kernel: smb_retry: signal failed, error=-3 
Nov 30 17:14:19 puma last message repeated 17 times

The problem occurs about once every two months.  Can you suggest anything
to put into the cron job to dump all relevant data?  Since it's a live
system, I'm not willing to leave it half-mounted until I get around to
fixing it.

Nancy Fudd -- nfudd at
"The percentage of users running Windows NT Workstation 4.0 whose PCs
 stopped working more than once a month was less than half that of Windows
 95 users."--

More information about the samba mailing list