From: "Jürgen Herrmann" <t-5@t-5.eu>
To: linux-btrfs@vger.kernel.org
Subject: btrfs send hangs after partial transfer and blocks all IO
Date: Thu, 13 Sep 2018 10:34:37 +0200 [thread overview]
Message-ID: <8c2c436d404bca00617614d08e9720c1@t-5.eu> (raw)
Hello!
I have a newly installed laptop running a freshly installed (abt. two
months ago) laptop running latest linux mint 19. Root filesystem is on a
1TB Samsung 860 M.2 SSD with btrfs on top of a LUKS encrypted 900G
partition. Timeshift-btrfs is enabled for root (@) and home (@home)
subvolumes. I want to transfer snapshots to a server with a separated
disk via "btrfs send" and ssh.
Here's the list of snapshot directories, each containing tow snapshots
for root and home:
drwxr-xr-x 1 root root 30 Sep 12 22:08 2018-08-16_20-00-01
drwxr-xr-x 1 root root 30 Aug 17 14:00 2018-08-17_14-00-02
drwxr-xr-x 1 root root 30 Aug 23 20:00 2018-08-23_20-00-01
drwxr-xr-x 1 root root 30 Aug 30 20:00 2018-08-30_20-00-01
drwxr-xr-x 1 root root 30 Sep 6 20:00 2018-09-06_20-00-01
drwxr-xr-x 1 root root 30 Sep 6 22:00 2018-09-06_22-00-01
drwxr-xr-x 1 root root 30 Sep 8 16:00 2018-09-08_16-00-01
drwxr-xr-x 1 root root 30 Sep 10 20:00 2018-09-10_20-00-02
drwxr-xr-x 1 root root 30 Sep 11 21:00 2018-09-11_21-00-02
drwxr-xr-x 1 root root 30 Sep 12 21:00 2018-09-12_21-00-01
"btrfs send
/mnt/timeshift/backup/timeshift-btrfs/snapshots/2018-08-16_20-00-01/@
>/dev/null" results in the btrfs task taking 100% cpu time on one cpu and then all IO is blocked -> only reboot can solve the hang.
The crash does not happen immediately, as i was on the road using
cellular connection it seemed fine at first. That's how I found out that
it transfers ~140MB of data before hanging. The snapshot is created on
the server and contains data (du shows abt 140MB).
I am running vanilla kernel 4.18.6 (compiled by myself) and btrfs progs
4.17.1 compiled from source.
Here's the btrfs filesystem info:
Label: none uuid: a914c141-72bf-448b-847f-d64ee82d8b7b
Total devices 1 FS bytes used 342.85GiB
devid 1 size 875.44GiB used 357.05GiB path
/dev/mapper/sda3_crypt
A scrub shows no errors:
scrub status for a914c141-72bf-448b-847f-d64ee82d8b7b
scrub started at Thu Sep 13 10:20:18 2018 and finished after
00:12:19
total bytes scrubbed: 342.78GiB with 0 errors
What can I do to help debugging this issue?
Best regards,
Jürgen
--
Jürgen Herrmann
https://t-5.eu
ALbertstraße 2
94327 Bogen
next reply other threads:[~2018-09-13 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 8:34 Jürgen Herrmann [this message]
2018-09-13 8:40 ` btrfs send hangs after partial transfer and blocks all IO Nikolay Borisov
2018-09-13 10:29 ` Jürgen Herrmann
2018-09-13 10:50 ` Nikolay Borisov
2018-09-13 10:56 ` Jürgen Herrmann
2018-09-13 11:04 ` Nikolay Borisov
2018-09-13 11:50 ` Jürgen Herrmann
2018-09-13 12:02 ` Nikolay Borisov
2018-09-13 12:30 ` Jürgen Herrmann
2018-09-13 12:35 ` Nikolay Borisov
2018-09-13 15:30 ` Chris Murphy
2018-09-13 15:44 ` Nikolay Borisov
2018-09-13 16:22 ` Chris Murphy
2018-09-19 19:35 ` Jürgen Herrmann
2018-09-19 19:41 ` Jürgen Herrmann
2018-09-20 17:25 ` Chris Murphy
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=8c2c436d404bca00617614d08e9720c1@t-5.eu \
--to=t-5@t-5.eu \
--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;
as well as URLs for NNTP newsgroup(s).