From: David Newall <btrfs@davidnewall.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Mount/df/PAM login hangs during rsync to btrfs subvolume, or maybe doing btrfs subvolume snapshot
Date: Wed, 11 Sep 2019 19:51:22 +0930 [thread overview]
Message-ID: <cfc872b2-ea1e-57b4-f548-48679daad069@davidnewall.com> (raw)
In-Reply-To: <1a651f17-ba40-2f17-403e-69999e927b2d@suse.com>
> echo w > /proc/sysrq-trigger
Interesting.
One material point which I failed to mention is that the btrfs volume is
on an encrypted volume (cryptsetup luksOpen /dev/vdc backups).
The first step, "mount -r /dev/vg/ext2fs-snapshot
/btrfs-backup-volume/local-snapshot", seemed to trigger the problem.
When I did the echo to sysrq-trigger, it seemed to stop blocking, but
that might have been a coincidence. After the echo, kernel output
exceeded 100KB, so I saved it to https://davidnewall.com/kern.1
During rsync (--archive --one-file-system --hard-links --inplace
--numeric-ids --delete /btrfs-backup-volume/local-snapshot/
/btrfs-backup-volume/data/), initially there was no problem, but, then
it (df) seemed to hang again. The rsync took a long time to complete,
and before it did finish, I did the echo to sysrq-trigger again; kernel
output is saved to https://davidnewall.com/kern.2
The rsync finished not long after the echo to sysrq-trigger, but that's
probably also a coincidence. After rsync completed, df still hung. I
did another echo to sysrq-trigger, and saved kernel output to
https://davidnewall.com/kern.3
I tried a minor change in procedure to see if it would bring the system
back to normal response. Normally I'd do "btrfs subvolume snapshot",
but I tried unmounting the lvm2 snapshot first (umount
/btrfs-backup-volume/local-snapshot). It did not complete within the
expected time, and another echo to sysrq-trigger resulted in
https://davidnewall.com/kern.4
Eventually the umount completed and system came back to normal response.
I did the btrfs subvolume snapshot, and it completed faster than I could
notice without causing any issues.
After unmounting the btrfs volume, I tried each step again, and
everything completed within expected times without causing any hang.
Something which I did previously mention, but I'll repeat because it
might well be important, is that the base ext2 filesystem is on a
drbd-replicated volume. I don't know if it's part of the problem, and I
observe that the hang condition was not triggered at the point of
creating the lvm2 snapshot.
I greatly appreciate your advice and help.
Thanks,
David
next prev parent reply other threads:[~2019-09-11 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 6:45 Mount/df/PAM login hangs during rsync to btrfs subvolume, or maybe doing btrfs subvolume snapshot David Newall
2019-09-11 6:55 ` Nikolay Borisov
2019-09-11 7:03 ` David Newall
2019-09-11 10:21 ` David Newall [this message]
2019-09-11 10:52 ` Nikolay Borisov
2019-09-12 4:38 ` David Newall
2019-09-12 6:11 ` Nikolay Borisov
2019-09-12 6:28 ` Nikolay Borisov
2019-09-12 7:05 ` Qu Wenruo
2019-09-12 14:03 ` David Newall
2019-09-12 14:12 ` Nikolay Borisov
2019-09-12 14:16 ` Qu Wenruo
2019-09-12 14:14 ` Qu Wenruo
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=cfc872b2-ea1e-57b4-f548-48679daad069@davidnewall.com \
--to=btrfs@davidnewall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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).