From: David Newall <btrfs@davidnewall.com>
To: Nikolay Borisov <nborisov@suse.com>,
David Newall <btrfs@davidnewall.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: Thu, 12 Sep 2019 14:08:07 +0930 [thread overview]
Message-ID: <d83709b8-7c0f-d3dd-7d6e-3bdbe08e144a@davidnewall.com> (raw)
In-Reply-To: <133d5657-a045-ad53-31f0-75714d983255@suse.com>
On 11/9/19 8:22 pm, Nikolay Borisov wrote:
>> I saved it tohttps://davidnewall.com/kern.1
> Nothing useful in that log, everything seems normal.
Thank you, again, for your help. I am grateful.
If I understand the output, both df and mount are waiting for
show_mountinfo which is waiting for btrfs_show_devname which is waiting
to get a lock. They have to wait to find the devname for ten minutes.
Is that really normal?
I'm not saying that btrfs is behind it, but it does seem like something
is not right.
I notice that there's a waiting btrfs-transation, too. I don't know
what the transaction would be, and no doubt it's completely appropriate,
even though the use of btrfs at that point is merely one mount (and one
mount of ext2 over a sub-directory, probably no involvement by btrfs.)
I see, too, that systemd is waiting for btrfs_show_devname. It's a
pattern.
I take your point about the kernel being somewhat old and accept that
I'm unlikely to get far without confirming the problem on a recent kernel.
next prev parent reply other threads:[~2019-09-12 4:38 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
2019-09-11 10:52 ` Nikolay Borisov
2019-09-12 4:38 ` David Newall [this message]
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=d83709b8-7c0f-d3dd-7d6e-3bdbe08e144a@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).