From: "Scott E. Blomquist" <sb@techsquare.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: "Scott E. Blomquist" <sb@techsquare.com>,
Jojo <jojo@automatix.de>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs hang on nfs?
Date: Thu, 10 Jan 2019 07:00:02 -0500 [thread overview]
Message-ID: <23607.13250.659000.140295@techsquare.com> (raw)
In-Reply-To: <f95b63e3-9da5-ea60-3b4c-fbdf223f439c@suse.com>
Nikolay Borisov writes:
> >
> > Unfortunately the cfq scheduler did not help. The system wedged.
> >
> > I did notice this for the first time...
> >
> > [Wed Jan 9 06:03:41 2019] BTRFS info (device sda1): the free space cache file (83320273633280) is invalid, skip it
>
> What you could do is mount btrfs with -o clear_cache to make btrfs
> rebuild the freespace cache.
>
> >
> > anything I should do about that?
> >
> > The messages were similar...
> >
> > [Wed Jan 9 23:52:04 2019] INFO: task nfsd:2997 blocked for more than 120 seconds.
> > [Wed Jan 9 23:52:04 2019] Not tainted 4.17.14-custom #1
> > [Wed Jan 9 23:52:04 2019] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > [stuff deleted]
> > [Wed Jan 9 23:54:07 2019] RBP: 00007f0c3f348c60 R08: 00000000000000ff R09: 0000000000001000
> > [Wed Jan 9 23:54:07 2019] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000a6672f
> > [Wed Jan 9 23:54:07 2019] R13: 00007f0c918affe0 R14: 0000000000000000 R15: 00007f0c918affb0
> >
>
> These don't tell the full story, what seems to be happening is that
> stuff is waiting for transaction to finish but it's not evident which
> thread is holding the transaction. Please, paste the output of
> "echo w > /proc/sysrq-trigger" so we have full picture of what's blocked
> where.
>
Thanks. I have not seen the free space cache message with the new
kernel.
Next time the hang pops up I'll echo w > /proc/sysrq-trigger and send
it along.
I am hoping that the new kernel will magically fix the problem.
Thanks again,
sb. Scott Blomquist
next prev parent reply other threads:[~2019-01-10 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 10:54 btrfs hang on nfs? Scott E. Blomquist
2019-01-09 12:14 ` Jojo
2019-01-09 13:31 ` Scott E. Blomquist
2019-01-10 11:46 ` Scott E. Blomquist
2019-01-10 11:51 ` Nikolay Borisov
2019-01-10 12:00 ` Scott E. Blomquist [this message]
2019-01-14 11:42 ` Scott E. Blomquist
2019-01-14 12:11 ` Nikolay Borisov
2019-01-14 13:13 ` Scott E. Blomquist
2019-01-14 13:28 ` Nikolay Borisov
2019-01-15 8:16 ` Nikolay Borisov
2019-01-15 14:36 ` Scott E. Blomquist
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=23607.13250.659000.140295@techsquare.com \
--to=sb@techsquare.com \
--cc=jojo@automatix.de \
--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).