linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Wettenhall <james.wettenhall@monash.edu>
To: linux-cifs@vger.kernel.org
Subject: Frequent reconnections / session startups?
Date: Mon, 26 Aug 2019 16:55:47 +1000	[thread overview]
Message-ID: <CAE78Er-YVBzqaf8jCBio_V_1J2kRiWZ_SH-HnHm7KG3t46=j6w@mail.gmail.com> (raw)

Hi,

We run a Django / Celery application which makes heavy use of CIFS
mounts.  We are experiencing frequent reconnections / session startups
and would like to understand how to avoid hammering the CIFS server
and/or the authentication server.  We've had multiple reports of
DoS-like hammering from server admins, causing frequent
re-authentication attempts and in one case causing core dumps on the
CIFS server.

Our CIFS client VMs have the following:

OS: Ubuntu 18.04.3
Kernel: 4.15.0-58-generic
mount.cifs: 6.8

Current mount options:
rw,relatime,vers=3.0,sec=ntlmssp,cache=strict,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1

We don't run the CIFS server, but we can request any information
required to diagnose the issue.

Over the past 10 hours, one of our virtual machine's kernel log has accumulated:

8453 kern.log messages including "CIFS"

To break that down, we have:

8305 "Free previous auth_key.response" messages
111 "validate protocol negotiate failed: -11" messages
26 "Close unmatched open" messages
7 "has not responded in 120 seconds" messages
4  "cifs_mount failed w/return code = -11" messages

The server is an HSM (Hierarchical Storage Management) system, so it
can be slow to respond if our application requests a file which is
only available on tape, not on disk.

The most common operation our application is performing on the
CIFS-mounted files is calculating MD5 checksums - with many Celery
worker processes running concurrently.

We would appreciate any advice on how to investigate further.

Thanks,
James

             reply	other threads:[~2019-08-26  6:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  6:55 James Wettenhall [this message]
2019-08-26 14:55 ` Frequent reconnections / session startups? Steve French
2019-08-28  1:50   ` James Wettenhall
2019-09-02  0:23   ` James Wettenhall
2019-09-03 10:38     ` Aurélien Aptel
2019-09-04  6:46       ` James Wettenhall
2019-09-13 23:47         ` Pavel Shilovsky
     [not found]           ` <CAE78Er97k7O-GDGdMtp0qXtQ-q-1nS_d1AE6HHH+Kz6PV_G2uQ@mail.gmail.com>
2019-09-18  5:23             ` James Wettenhall
2019-09-18  6:49               ` ronnie sahlberg
2019-09-18 17:58                 ` Pavel Shilovsky

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='CAE78Er-YVBzqaf8jCBio_V_1J2kRiWZ_SH-HnHm7KG3t46=j6w@mail.gmail.com' \
    --to=james.wettenhall@monash.edu \
    --cc=linux-cifs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).