[lkml]   [1999]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: smbfs problem with 2.2.5
"Steven N. Hirsch" wrote:
> On Tue, 13 Apr 1999, Markus Fischer wrote:
> > When mounting shares, i can access them without problems, but
> > after some time ( not more than 5 or 10 minutes) i can't access
> > the shares anymore. Any access try results in a "i/o errror".
> I'm seeing the same thing here, for another data point.
> Steve

I was seeing the same thing too, for a while. Now, my NT box doesn't
stay up long enough to really run a test.

One thing a friend down the road has done to work around this problem
(because he requires 24/7 uninterrupted service) is to daemonize a df
process in a while loop:

while : ; do
df --sync --type=smbfs >> /dev/null;
sleep 123;

This would cause NT to think that something was actually accessing the
share, and interpret it as activity. For some reason "ls" doesn't do
that, probably because dir info is cached on the client, and so doesn't
always access the physical NT share when performed.

What would be nice is for samba to check every once in a while that
shares are still mounted, and if they aren't, remount them, or generate
a solid "keepalive", or something. Also nice would be if smbmount
detects the IO error, to check if the share is unavailable, and if it is
unavailable, to automatically unmount the share. As it is, you have to
su to root and do a umount on the directory that is supposedly mounted,
because smbumount won't work in this case.

If you look in the kernel code, you can see where the log error messages
are generated, but I'm still not sure how the kernel knows to generate
those messages...i.e., where/when the smbfs message functions get called
from, and after what check.
Matthew Vanecek
Course of Study:
Visit my Website at
For answers type: perl -e 'print
For 93 million miles, there is nothing between the sun and my shadow
except me. I'm always getting in the way of something...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:51    [W:0.075 / U:2.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site