From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: L A Walsh <cifs-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>,
linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: cifs running amok after being disconnected (timeout?)
Date: Tue, 28 Feb 2017 11:52:38 +0100 [thread overview]
Message-ID: <mpslgsqfuyx.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <58B48122.5000708-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
Hi,
L A Walsh <cifs-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org> writes:
> I tried turning on debug by echoing 1 to /proc/fs/cifs/traceSMB, and that
> "effectively" stopped the conversation, as it was then saturating my
> message log with lines like:
enabling traceSMB just does a hexdump of every packet sent on the
wire. You probably want this:
echo 1 > /proc/fs/cifs/cifsFYI
echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
with CONFIG_CIFS_DEBUG, CONFIG_CIFS_DEBUG2, CONFIG_DYNAMIC_DEBUG enabled.
> Any idea what might have been going on? Anything better tracing
> options to determine what was going on?
As you said it seems the server keeps reseting the tcp connexion. A full
trace starting from the initial mount will help.
You should be able to open a bug on either samba on the kernel
bugtracker and attach traces there.
Have you tried to mount using a newer protocol (2.1 or 3.0)? (using
e.g. -o vers=2.1)
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-02-28 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:42 cifs running amok after being disconnected (timeout?) L A Walsh
[not found] ` <58B48122.5000708-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-02-28 10:52 ` Aurélien Aptel [this message]
[not found] ` <mpslgsqfuyx.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-02-28 21:58 ` L A Walsh
[not found] ` <58B5F296.1080408-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-03-01 11:29 ` Aurélien Aptel
[not found] ` <mpsefyhfd6b.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-03-01 18:06 ` L A Walsh
[not found] ` <58B70DB3.6010102-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-03-02 14:24 ` Aurélien Aptel
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=mpslgsqfuyx.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=cifs-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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