All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Robert Kudyba <rkudyba-tzaSEmCkE7qVc3sceRu5cw@public.gmane.org>,
	linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Fwd: backing up to a Drobo CIFS VFS: Error -11 sending data on socket to server, Bufferbloat?
Date: Fri, 12 May 2017 13:49:11 +0200	[thread overview]
Message-ID: <mpsinl6cn2g.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <CAFHi+KQhXFrOVDb51fZCs1e5ik3RY+v91H5Sz1Z3YkgUpMPURw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Robert,

The capture you posted unfortunately does not contain anything of worth
looking at I think. Only 2 SMB packets.

% tshark -r capture.pcap -Y 'smb||smb2'
   1130  15.032933 150.108.64.56 → 150.108.68.23 SMB 144 Trans2 Request, QUERY_PATH_INFO, Query File All Info, Path:
   1131  15.034786 150.108.68.23 → 150.108.64.56 SMB 204 Trans2 Response, QUERY_PATH_INFO

Given your kernel log message I would expect seeing the reconnecting happen.

I would wrap your backup script like so to get the right capture:

    capfile="$(date -Ihours)"
    tcpdump -w "$capfile" port 445 &
    cappid=$!
    sleep 2
    .....<your script>....
    sleep 2
    kill -6 $cappid


-- 
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)

  parent reply	other threads:[~2017-05-12 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B0AAEC04-DBAE-49AB-A549-B772D5F1B7F6@fordham.edu>
2017-05-11 20:42 ` backing up to a Drobo CIFS VFS: Error -11 sending data on socket to server, Bufferbloat? Robert Kudyba
     [not found]   ` <D5627D5A-065B-4C28-B152-7B0A587A0CBF-tzaSEmCkE7qVc3sceRu5cw@public.gmane.org>
2017-05-11 22:56     ` Richard Sharpe
     [not found]       ` <CAFHi+KS6HtBGvqTJxNgMYvBaYnibryf==5x8FTJfGtjMJOSkBA@mail.gmail.com>
     [not found]         ` <CAFHi+KRGNSvfgj7o+tK0RZZa9Nf2NQANUiygsUR5aokJH5NP7w@mail.gmail.com>
     [not found]           ` <CAFHi+KSB348xPhYSf=x7FW9kmgU5iN-mDGvs2Fhyv=UYCMQckw@mail.gmail.com>
     [not found]             ` <CAFHi+KRjK-pLxr+gNkE0jpsM1YfgE4s2Lw8Q4XTSTP-V0_Ds8A@mail.gmail.com>
     [not found]               ` <CAFHi+KRjK-pLxr+gNkE0jpsM1YfgE4s2Lw8Q4XTSTP-V0_Ds8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-12  2:37                 ` Fwd: " Robert Kudyba
     [not found]                   ` <CAFHi+KQhXFrOVDb51fZCs1e5ik3RY+v91H5Sz1Z3YkgUpMPURw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-12 11:49                     ` Aurélien Aptel [this message]
     [not found]                       ` <mpsinl6cn2g.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-05-12 13:45                         ` Robert Kudyba

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=mpsinl6cn2g.fsf@aaptelpc.suse.de \
    --to=aaptel-ibi9rg/b67k@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rkudyba-tzaSEmCkE7qVc3sceRu5cw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.