smbmount intermittent problems

[Hieb, Michael]

I use smbmount to mount a number of NT shares from around a global network
in order to sync from a master distribution which resides in linux.
Specifically...

uklnxsrv$ smbmount //NTSRV/share -c 'mount /tmp/temporary_mount -u 502 -g
510' -U guest%guest_passwd

Frequently it works well, but from time to time the mounted NT share, for
lack of a better word gets corrupted. Here are the symptons

1.	trying to access the directory gives the following error.

		uklnxsrv$ ls -la /tmp/temporary_mount
		ls: /tmp/temporary_mount: lstat failed: Input/output error

2.	If you try to access /tmp you do not see the mount, but get the same
error...

		uklnxsrv$ ls -la /tmp
		ls: /tmp/temporary_mount: Input/output error
		total 2
		drwxr-xr-x   3 aigfpdev aigfpdev     1024 Jul 14 08:00 .
		drwxrwxrwx   3 aigfpdev aigfpdev     1024 Jul 14 07:57 ..

3.	The smbmount cannot be removed by smbumount, if you try smbumount
will return without an error, but the corrupted mount will still be there.
Only rebooting the linux machines (shudder...) seems to remove the mount..


4.	Syslog reports the following errors

	Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 
	Jul 14 05:23:51 uklnxsrv kernel: smb_lookup: find //Risk failed,
error=-5 
	Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 
	Jul 14 05:23:51 uklnxsrv kernel: smb_lookup: find //Risk failed,
error=-5 
	Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 
	Jul 14 05:23:51 uklnxsrv kernel: smb_lookup: find //Risk failed,
error=-5 
	Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 
	Jul 14 05:23:51 uklnxsrv kernel: smb_retry: signal failed, error=-3 
	Jul 14 05:23:51 uklnxsrv rdist[27307]: uklnxsrv: REMOTE ERROR:
/tmp/temporary_mount/document.doc: lstat failed: Input/output error


The network is fairly slow <250 Kbs/sec, the problem is intermittent and not
always between London and Tokyo, sometimes to New York, sometimes to Paris,
etc...

I am using RH6.0 and Samba 2.0.3-8.

Please help, what is wrong, how can I deal with it?