Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: linux-btrfs@vger.kernel.org
Subject: Timeouts copying large files to a Samba server with Btrfs
Date: Sun, 20 Dec 2015 02:50:10 +0500	[thread overview]
Message-ID: <20151220025010.7d353d35@natsu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

Hello,

Sometimes when I copy large files (the latest case was with a 13 GB file) to a
Btrfs-residing share on a Samba file server (using Thunar file manager), the
copy process fails around the end with following messages in dmesg on the
client:

[7699154.504380] CIFS VFS: sends on sock ffff88010d41e800 stuck for 15 seconds
[7699154.504440] CIFS VFS: Error -11 sending data on socket to server
[7699215.173469] CIFS VFS: sends on sock ffff88010d41e800 stuck for 15 seconds
[7699215.173533] CIFS VFS: Error -11 sending data on socket to server
[7699317.982262] CIFS VFS: sends on sock ffff88010d41e800 stuck for 15 seconds
[7699317.982319] CIFS VFS: Error -11 sending data on socket to server

Nothing in dmesg on the server.

My guess is that the Samba server process submits too much queued buffers at
once to be written to disk, then blocks on waiting for this, and the whole
operation ends up taking so long, that it doesn't get back to the client in
time.

This also happens much more often is compress-force is enabled on the server.

The server specs are AMD E-350 1.6GHz, 16GB of RAM, client/server network
connection is 1 Gbit. Kernel 4.1.15 on the server, 3.18.21 on the client.

Any idea what to tune so that this doesn't happen? (server/client/Samba/Btrfs?)

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-12-19 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 21:50 Roman Mamedov [this message]
2015-12-26 14:54 ` Timeouts copying large files to a Samba server with Btrfs Piotr Pawłow
2015-12-26 17:50 ` ronnie sahlberg

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=20151220025010.7d353d35@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@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