From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Cc: Cameron Harris <thecwin@gmail.com>, akpm@osld.org
Subject: Re: cifs connection loss hangs
Date: Mon, 21 Feb 2005 09:35:44 -0600 [thread overview]
Message-ID: <4219FFD0.8050008@austin.rr.com> (raw)
>Being a wireless user i experience the occasional connection loss due
>to walking out of range or something, recently after starting to use
>cifs mounts instead of smbfs, I've noticed that stuff tends to break
> if i lose connection.
cifs does support reconnection after tcp session drops (including
reattaching to the server shares and reopening open files, rewriting
cached data).
What kernel version ("cat /proc/version") or cifs vfs version ("modinfo
/lib/modules/<kernel ver>/kernel/fs/cifs/cifs.ko) are you running?
2.6.10 includes one fix for a race in the cifs reconnection logic (which
is included in cifs version 1.27 or later) and there was an earlier (and
more important) reconnection fix in cifs version 1.10 (I think that came
in mainline about at kernel version 2.6.6).
There are test patches (or in some cases a copy of the fs/cifs
directory) available for a few of the older but common kernels (SLES9,
SuseWorkstation 9.2, FC3 etc.) at
http://us1.samba.org/samba/ftp/cifs-cvs which include up to 2.6.10 level.
Note that you can view the state of cifs connections by "cat
/proc/fs/cifs/DebugData" (also interesting is "cat /proc/fs/cifs/Stats")
which will show the cifs tcp sessions, smb sessions and tree connection
(mount) and whether they need reconnection - it also shows the state of
any pending [cifs] operations on the network.
next reply other threads:[~2005-02-21 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 15:35 Steve French [this message]
2005-02-21 20:09 ` cifs connection loss hangs Cameron Harris
-- strict thread matches above, loose matches on Subject: below --
2005-02-20 23:09 Cameron Harris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4219FFD0.8050008@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=akpm@osld.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thecwin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox