smbfs problems

[Frank Carreiro]

I've run into a problem with smbfs.  Apparently after a user mounts a 
win2k share the mount directory will disappear and if they cd and type 
"ls" they receive an i/o error message.  I've checked my message logs 
and see several messages which I believe indicate we have a problem.  
I'm attaching our message log in the hope someone may be able to give me 
some direction here.

Originally I thought it was a problem with my 
/usr/src/linux/fs/smbfs/proc.c source code.  The time-out value is 5 
seconds.  I've increased this to 30 seconds and recompiled my kernel 
(running RedHat 6.2 - 2.2.14-5.0 kernel) .  Didn't seem to make a 
difference.  I'm wondering if there is something else I should be 
looking at.  I've checked Micro$ofts site and found a document "How the 
Auto disconnect Works with Windoze NT".  I believe this "could" be the 
culprit but before I change my auto disconnect on the Windwoes server 
I'd like to hear what other's have done to resolve this problem (in case 
I'm barking up the wrong tree again).

If this is the wrong list feel free to kindly direct me.  I'm not sure 
which group to direct this to.

Thx

Frank
-------------- next part --------------
Apr  3 09:18:51 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  3 09:18:51 testapp_002 kernel: smb_retry: new pid=1244, generation=2 
Apr  3 10:21:28 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  3 10:21:29 testapp_002 kernel: smb_retry: new pid=1244, generation=3 
Apr  3 10:55:48 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  3 10:55:48 testapp_002 kernel: smb_retry: new pid=1244, generation=4 
Apr  3 11:45:03 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  3 11:45:04 testapp_002 kernel: smb_retry: new pid=1244, generation=5 
Apr  3 16:27:26 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  3 16:27:27 testapp_002 kernel: smb_retry: new pid=1244, generation=6 
Apr  4 04:02:22 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  4 04:02:22 testapp_002 kernel: smb_retry: new pid=1244, generation=7 
Apr  4 07:54:01 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  4 07:54:02 testapp_002 kernel: smb_retry: new pid=1244, generation=8 
Apr  4 08:46:14 testapp_002 kernel: smb_get_length: recv error = 104 
Apr  4 08:46:14 testapp_002 kernel: smb_trans2_request: result=-104, setting invalid 
Apr  4 08:46:14 testapp_002 kernel: smb_retry: new pid=1244, generation=9 
Apr  4 09:47:43 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  4 09:48:02 testapp_002 kernel: KERN_INFO: caught signal 
Apr  4 09:48:03 testapp_002 kernel: KERN_INFO: caught signal 
Apr  4 09:48:05 testapp_002 kernel: smb_retry: signal failed, error=-3 
Apr  4 09:48:50 testapp_002 last message repeated 3 times
Apr  4 09:51:29 testapp_002 kernel: smb_retry: signal failed, error=-3 
Apr  4 09:51:32 testapp_002 last message repeated 2 times
Apr  4 10:01:08 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  4 10:01:08 testapp_002 kernel: smb_retry: new pid=1244, generation=10 
Apr  4 10:30:19 testapp_002 kernel: smb_retry: signal failed, error=-3 
Apr  4 11:08:35 testapp_002 kernel: smb_trans2_request: result=-32, setting invalid 
Apr  4 11:08:35 testapp_002 kernel: smb_retry: new pid=1244, generation=11