From: Roman Mamedov <rm@romanrm.net>
To: Cheyenne Wills <cheyenne.wills@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Need some assistance/direction in determining a system hang during heavy IO
Date: Thu, 26 Oct 2017 22:41:48 +0500 [thread overview]
Message-ID: <20171026224148.57e4d035@natsu> (raw)
In-Reply-To: <CAHpsFVc8a-2ARN+ESza8e1MYhDk5okww9b0K2DAy9QXeiPQsBw@mail.gmail.com>
On Thu, 26 Oct 2017 09:40:19 -0600
Cheyenne Wills <cheyenne.wills@gmail.com> wrote:
> Briefly when I upgraded a system from 4.0.5 kernel to 4.9.5 (and
> later) I'm seeing a blocked task timeout with heavy IO against a
> multi-lun btrfs filesystem. I've tried a 4.12.12 kernel and am still
> getting the hang.
There is now 4.9.58 (fifty three versions later!) and 4.12 series is long
abandoned and gone from the charts altogether. So just in case, did you check
with the latest kernels?
Also, keep in mind the 120 second warnings are just that, and not an error
condition by themselves. You can disable them or increase the maximum timeout
in sysctl settings. And it is not clear from your reports if you only get
warnings and after the load subsides everything is back to normal, or the FS
locks out "for good", i.e. with all access attempts hanging indefinitely and
no way to unmount the FS or otherwise recover.
--
With respect,
Roman
next prev parent reply other threads:[~2017-10-26 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 15:40 Need some assistance/direction in determining a system hang during heavy IO Cheyenne Wills
2017-10-26 17:41 ` Roman Mamedov [this message]
2017-10-26 18:04 ` Cheyenne Wills
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=20171026224148.57e4d035@natsu \
--to=rm@romanrm.net \
--cc=cheyenne.wills@gmail.com \
--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